From: Ben Gamari <bgamari.foss@gmail.com>
Cc: balbi@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030
Date: Wed, 19 Jan 2011 15:04:13 -0500 [thread overview]
Message-ID: <874o947j9e.fsf@gmail.com> (raw)
In-Reply-To: <20110119034528.GA2406@legolas.emea.dhcp.ti.com>
On Wed, 19 Jan 2011 05:45:28 +0200, Felipe Balbi <balbi@ti.com> wrote:
> The point is, being able to disable features I don't want on my kernel
> image, is completely valid, if there's a compile breakage, then fix the
> breakage but don't prevent the board from compiling.
>
I understand. That being said, Linus has made it well known that
defconfigs will not be an option going forward. Have we found another
means of selecting the basic drivers necessary to get a fully functional
board? Perhaps a CONFIG_MACH_OMAP3_BEAGLE_CORE option selecting the
necessary driver for a fully functional board would be a solution. I
remember this being discussed several months ago (when Linus started
pulling defconfigs out of the tree), but I don't recall there being any
replacement proposals. It should be possible to build a functional
kernel from the mainline without iterating over all available
configuration options.
- Ben
next prev parent reply other threads:[~2011-01-19 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:25 [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030 Ben Gamari
2011-01-18 3:10 ` Felipe Balbi
2011-01-18 13:51 ` Ben Gamari
2011-01-19 3:45 ` Felipe Balbi
2011-01-19 20:04 ` Ben Gamari [this message]
2011-01-20 4:08 ` Felipe Balbi
2011-01-20 17:27 ` Tony Lindgren
2011-01-20 21:44 ` Ben Gamari
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=874o947j9e.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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