kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
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:07:12 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1605040758450.19704@localhost.localdomain> (raw)


  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"?

  i ask because i'm putting together some kernel configuration
fragments that will contribute to a final .config file and, because of
all that "default y" stuff, i explicitly have to add "is not set"
lines to my fragments to turn off all the vendors in which i have no
interest.

  admittedly, as i read it, leaving them as "default y" doesn't seem
to generate any additional code unless you actually select a board
from that vendor; still, is there a reason the Kconfig files are set
up the way they are?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

             reply	other threads:[~2016-05-04 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 12:07 Robert P. J. Day [this message]
2016-05-04 12:42 ` what is the rationale for all ethernet device vendors being "default y"? Bjørn Mork
2016-05-04 12:44   ` Robert P. J. Day
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.1605040758450.19704@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).