Message ID | 1484610.g1p0X99tcV@wuerfel |
---|---|
State | New |
Headers | show |
On Tue, Nov 22, 2011 at 10:19:53PM +0100, Arnd Bergmann wrote: > and then selecting DEBUG_LL_LEGACY from all platforms that do their own > thing. That would avoid the possible randconfig errors. Your fix seems good to me, and avoids causing hassle for randconfig folks, though Russell's will be more likely to encourage people to convert I guess.
On Tue, Nov 22, 2011 at 11:00:31PM +0000, Mark Brown wrote: > On Tue, Nov 22, 2011 at 10:19:53PM +0100, Arnd Bergmann wrote: > > > and then selecting DEBUG_LL_LEGACY from all platforms that do their own > > thing. That would avoid the possible randconfig errors. > > Your fix seems good to me, and avoids causing hassle for randconfig > folks, though Russell's will be more likely to encourage people to > convert I guess. Although Russell's approach is a build breaker for those platforms that have not yet made the switch, that does provide an incentive for the platform maintainers to update their code. If we settle for a legacy solution it will probably sit around forever. Given that we're now past -rc2, it might be best to wait until the next merge window to introduce the #error logic, so the LEGACY solution could be a stopgap for 3.2. Will
--- a/arch/arm/Kconfig.debug +++ b/arch/arm/Kconfig.debug @@ -83,6 +83,8 @@ choice depends on DEBUG_LL config DEBUG_LL_UART_NONE + depends on !FOOTBRIDGE && !ARCH_CLPS711X && !ARCH_MXC && \ + !PLAT_SAMSUNG && !ARCH_REALVIEW && !ARCH_HIGHBANK bool "No low-level debugging UART" help Say Y here if your platform doesn't provide a UART option