From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: omap defconfigs in mainline tree Date: Fri, 7 Apr 2006 06:14:32 -0700 Message-ID: <20060407131430.GD21950@atomide.com> References: <20060407093134.25516.qmail@web32902.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060407093134.25516.qmail@web32902.mail.mud.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Komal Shah Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Komal Shah [060407 02:31]: > Tony, > > I want to understand why we don't push defconfigs (minus drivers > options, which are not yet in mainline) to mainline tree? If we do that > we can cover all variants as part of kautobuild, _or_ if someone gives > me idea on setting up such autobuilds (kautobuild source?) I can set it > up offline here. We should send them, but let's get the omap i2c driver integrated first. Then the mainline tree will be usable too. Tony