From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: what is the rationale for all ethernet device vendors being "default y"?
Date: Wed, 4 May 2016 08:44:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605040844210.20421@localhost.localdomain> (raw)
In-Reply-To: <87twiekn9l.fsf@nemi.mork.no>
On Wed, 4 May 2016, Bj?rn Mork wrote:
> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
> > just noticed that on my x86 system, when i do a:
> >
> > $ make defconfig
> >
> > under "Ethernet driver support", all the top-level vendor choices
> > (3com, adaptec and so on) all have Kconfig entries with:
> >
> > default y
> >
> > reasonably, for each vendor, all of their cards are not "default y"
> > (that would be kind of silly), but what is the logic behind making
> > each vendor selection "default y"?
>
> To avoid introducing build regressions with the introduction of these
> directories:
> http://lists.openwall.net/netdev/2011/08/23/41
>
> This is because these directories were retro-fitted to the Kbuild system
> for most ethernet drivers.
ah, makes perfect sense, thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-05-04 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 12:07 what is the rationale for all ethernet device vendors being "default y"? Robert P. J. Day
2016-05-04 12:42 ` Bjørn Mork
2016-05-04 12:44 ` Robert P. J. Day [this message]
2016-05-04 13:05 ` Robert P. J. Day
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=alpine.LFD.2.20.1605040844210.20421@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.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).