From: bgamari.foss@gmail.com (Ben Gamari)
Date: Wed, 19 Jan 2011 15:04:13 -0500
Subject: [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030
In-Reply-To: <20110119034528.GA2406@legolas.emea.dhcp.ti.com>
References: <1295299548-22839-1-git-send-email-bgamari.foss@gmail.com>
	<20110118031038.GA2436@legolas.emea.dhcp.ti.com>
	<87d3nus4jr.fsf@gmail.com>
	<20110119034528.GA2406@legolas.emea.dhcp.ti.com>
Message-ID: <874o947j9e.fsf@gmail.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

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