From: David Miller <davem@davemloft.net>
To: lacombar@gmail.com
Cc: sfr@canb.auug.org.au, mikey@neuling.org,
linux-kbuild@vger.kernel.org, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, paulus@samba.org,
jeffrey.t.kirsher@intel.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: linux-next: boot test failure (net tree)
Date: Mon, 22 Aug 2011 21:02:55 -0700 (PDT) [thread overview]
Message-ID: <20110822.210255.1902105215409964106.davem@davemloft.net> (raw)
In-Reply-To: <CACqU3MW4BnucRt3gxPrKPDvWEjaVuxRF1VOPWk5hTRfneyANkg@mail.gmail.com>
From: Arnaud Lacombe <lacombar@gmail.com>
Date: Mon, 22 Aug 2011 23:50:02 -0400
> Are you implying we need some kind of way to migrate config ?
The issue is that the dependencies for every single ethernet driver
have changed. Some dependencies have been dropped (f.e. NETDEV_10000
and some have been added (f.e. ETHERNET, NET_VENDOR_****)
So right now an automated (non-prompted, default to no on all new
options) run on an existing config results in all ethernet drivers
getting disabled because the new dependencies don't get enabled.
This wouldn't be so bad if it was just one or two drivers, but in
this case it's every single ethernet driver which will have and hit
this problem.
next prev parent reply other threads:[~2011-08-23 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110816.171525.639251389938336183.davem@davemloft.net>
[not found] ` <20110817105002.efebf85d08460ad99b14be8e@canb.auug.org.au>
[not found] ` <20110818152214.661858a61496993aaef2c704@canb.auug.org.au>
[not found] ` <20110817.225356.1790362313048139752.davem@davemloft.net>
2011-08-22 1:30 ` linux-next: boot test failure (net tree) Stephen Rothwell
2011-08-23 1:40 ` Stephen Rothwell
2011-08-23 1:41 ` Stephen Rothwell
2011-08-23 2:13 ` David Miller
2011-08-23 2:26 ` Jeff Kirsher
2011-08-23 3:50 ` Arnaud Lacombe
2011-08-23 4:02 ` David Miller [this message]
2011-08-23 8:29 ` Jeff Kirsher
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=20110822.210255.1902105215409964106.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).