public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. dc735c40c38315b8c11f9c99c22cff9000c286f7
Date: Sun, 23 Jun 2013 08:39:32 +0200	[thread overview]
Message-ID: <20130623063934.20B6E20621@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  dc735c40c38315b8c11f9c99c22cff9000c286f7 (commit)
      from  6a9fcb7a73510a49ebe14f951b206733b0faf132 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit dc735c40c38315b8c11f9c99c22cff9000c286f7
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Jun 23 08:37:06 2013 +0200

    e1000e: disabled vendor modul on kirkwood.
    
    e1000e vendor driver does not build with a error at power management. So we use the default kernel driver on this platform.

-----------------------------------------------------------------------

Summary of changes:
 make.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/make.sh b/make.sh
index f3c4a58..9d93f07 100755
--- a/make.sh
+++ b/make.sh
@@ -442,7 +442,7 @@ buildipfire() {
     ipfiremake r8169			KCFG="-kirkwood"
     ipfiremake r8168			KCFG="-kirkwood"
     ipfiremake r8101			KCFG="-kirkwood"
-    ipfiremake e1000e			KCFG="-kirkwood"
+#    ipfiremake e1000e			KCFG="-kirkwood"
     ipfiremake igb			KCFG="-kirkwood"
 
   fi


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2013-06-23  6:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130623063934.20B6E20621@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox