[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120109095903.GC14252@pengutronix.de>
Date: Mon, 9 Jan 2012 10:59:03 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-kernel@...r.kernel.org, Alan Cox <alan@...ux.intel.com>,
devicetree-discuss@...ts.ozlabs.org,
Greg Kroah-Hartman <gregkh@...e.de>, kernel@...gutronix.de,
linux-serial@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Kconfig option for compile time build coverage (Was: Re: [PATCH]
serial/efm32: add new driver)
Hello,
On Fri, Dec 23, 2011 at 09:44:28PM +0100, Uwe Kleine-König wrote:
> On Fri, Dec 23, 2011 at 10:35:22AM +0000, Arnd Bergmann wrote:
> > On Thursday 22 December 2011, Uwe Kleine-König wrote:
> > > [...]
> > > +config SERIAL_EFM32_USART
> > > + bool "EFM32 USART port."
> > > + depends on ARCH_EFM32
> > > + select SERIAL_CORE
> [...]
> > I would generally prefer not to make the driver depend on the
> > platform, so we can get better compile time coverage. I think a better
> > set of dependencies would be
> >
> > depends on HAVE_CLK
> > depends on OF
> > default ARCH_EFM32
> I'd prefer something like:
>
> depends on HAVE_CLK
> depends on ARCH_EFM32 || I_DO_BUILD_COVERAGE_TESTING
>
> This would make it easier for Joe User to pick the right options for his
> kernel (assuming he found out to better keep I_DO_BUILD_COVERAGE_TESTING
> disabled). [...]
What do you think about this I_DO_BUILD_COVERAGE_TESTING option? It
would allow testers to get all possible options enabled (though there
will never be an EFM32 USART port on a non-EFM32 machine I guess) and
still users and distribution packagers would easily keep the option off
even without cluttering .config and {menu,n,x,whatever}config.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists