Linux backports project
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@kpanic.de>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: mcgrof@kernel.org, backports@vger.kernel.org
Subject: Re: [PATCH RFC 01/10] backports: add igb ethernet network driver
Date: Fri, 13 Dec 2013 08:39:06 +0100	[thread overview]
Message-ID: <52AAB99A.9080204@kpanic.de> (raw)
In-Reply-To: <52AA5485.50001@hauke-m.de>

On 13.12.2013 01:27, Hauke Mehrtens wrote:
> On 12/12/2013 10:27 AM, Stefan Assmann wrote:
>> - add igb to copy-list
>> - add igb defconfig
>> - refactor u64_stats_sync.h a bit
>> - add u64_stats_init define
>>
>> Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
>> ---

[...]

>> diff --git a/backport/defconfigs/igb b/backport/defconfigs/igb
>> new file mode 100644
>> index 0000000..1f85f18
>> --- /dev/null
>> +++ b/backport/defconfigs/igb
>> @@ -0,0 +1,7 @@
>> +CPTCFG_NETDEVICES=y
>> +CPTCFG_NET_ETHERNET=y
>> +CPTCFG_NETDEV_1000=y
>> +CPTCFG_ETHERNET=y
>> +CPTCFG_NET_VENDOR_INTEL=y
>> +CPTCFG_PCI=y
>> +CPTCFG_IGB=m
> 
> PCI should not be selected here, because it has to be selected in the
> kernel you are compiling against. I have not analyzed this, but I thing
> the defconfig should just contain these two options, the others should
> be already activated in the kernel:
> 
> CPTCFG_NET_VENDOR_INTEL=y
> CPTCFG_IGB=m

I'll see if I can boil this down. I had some trouble with older kernel
to get igb recognized.

  Stefan

> 
>> diff --git a/copy-list b/copy-list
>> index 9444aff..2b2e177 100644
>> --- a/copy-list
>> +++ b/copy-list
>> @@ -100,6 +100,10 @@ drivers/net/ethernet/broadcom/Makefile
>>  drivers/net/ethernet/broadcom/b44.c
>>  drivers/net/ethernet/broadcom/b44.h
>>  
>> +drivers/net/ethernet/intel/Kconfig
>> +drivers/net/ethernet/intel/Makefile
>> +drivers/net/ethernet/intel/igb/
>> +
> 
> This should be added in the last patch otherwise backports will not
> compile between this patch and the last one, becaise some parts are missing.
> 

Right, this was only a RFC and to see what breaks I had to enable it
early. :)

  Stefan

  reply	other threads:[~2013-12-13  7:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12  9:27 [PATCH RFC 00/10] backports: add igb driver Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 01/10] backports: add igb ethernet network driver Stefan Assmann
2013-12-13  0:27   ` Hauke Mehrtens
2013-12-13  7:39     ` Stefan Assmann [this message]
2013-12-12  9:27 ` [PATCH RFC 02/10] backports: igb fixes for linux-3.9 Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 03/10] backports: igb fixes for linux-3.8 Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 04/10] backports: igb fixes for linux-3.7 Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 05/10] backports: igb fixes for linux-3.6 Stefan Assmann
2013-12-13  0:46   ` Hauke Mehrtens
2013-12-13  8:01     ` Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 06/10] backports: igb fixes for linux-3.5 Stefan Assmann
2013-12-12  9:27 ` [PATCH RFC 07/10] backports: igb fixes for linux-3.4 Stefan Assmann
2013-12-12  9:28 ` [PATCH RFC 08/10] backports: igb fixes for linux-3.3 Stefan Assmann
2013-12-12  9:28 ` [PATCH RFC 09/10] backports: igb fixes for linux-3.2 Stefan Assmann
2013-12-12  9:28 ` [PATCH RFC 10/10] backports: igb fixes for linux-3.1 Stefan Assmann

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=52AAB99A.9080204@kpanic.de \
    --to=sassmann@kpanic.de \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=mcgrof@kernel.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