[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110822.210255.1902105215409964106.davem@davemloft.net>
Date: Mon, 22 Aug 2011 21:02:55 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: lacombar@...il.com
Cc: sfr@...b.auug.org.au, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
jeffrey.t.kirsher@...el.com, mikey@...ling.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linuxppc-dev@...ts.ozlabs.org, benh@...nel.crashing.org,
paulus@...ba.org, linux-kbuild@...r.kernel.org
Subject: Re: linux-next: boot test failure (net tree)
From: Arnaud Lacombe <lacombar@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists