All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: which drivers subdirs should be automatically selected?
Date: Tue, 22 Dec 2009 10:02:40 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912221000250.4427@localhost> (raw)


drivers/Makefile:

obj-y   += net/
obj-y   += serial/
obj-y   += nand/
obj-y   += nor/
obj-y   += usb/
obj-$(CONFIG_SPI) += spi/
obj-$(CONFIG_I2C) += i2c/
obj-$(CONFIG_VIDEO) += video/


  is there a fundamental reason that some of those subdirs are
auto-selected, while others are based on a CONFIG variable?  asked
another way, are there some driver subdirs that are so fundamentally
required that they *should* be auto-selected, or should *everything*
be a user-selectable choice?  the above just seems slightly
inconsistent and non-obvious.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2009-12-22 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 15:02 Robert P. J. Day [this message]
2009-12-22 15:23 ` which drivers subdirs should be automatically selected? Robert Schwebel
2009-12-22 15:30   ` Robert P. J. Day
2009-12-23  9:06 ` Sascha Hauer
2009-12-23  9:11   ` Robert Schwebel
2009-12-23  9:19   ` 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.00.0912221000250.4427@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.