Re: [PATCH] build some drivers only when compile-testing

On 06/18/2013 10:51 AM, Felipe Balbi wrote:

right, but my argument is that I rather not have either. Depend on
PCI if you us PCI, depend on EXTCON if you use extcon, but no
driver should have an ARCH dependency. Specially since it lets
people include mach/* and asm/* headers because "it doesn't break
compilation for anyone".

The argument is elsewhere. If I understand correctly, Kconfig is for
users, not to be hi-jacked by kernel developers. And users should not
really care about our development processes, cross compilations or
whatever bells and whistles we use. They just don't want to see
drivers which they have no way to *use*, they indeed don't care
whether some more compile at all. We do not want every kernel packager
for every distro out in the wild, to go through all the help texts, to
see whether they should compile and package a driver or not. It's a
tedious work and this option would save time to the packagers.

Try to package and maintain a kernel for a distribution, you will find
out what a cool and surprising work that is...

In the best case I would vote for hard dependencies as cross-compilers
are easy to obtain and set up nowadays. But well, we still want to
("cross") compile drivers, so let's add COMPILE_TEST and use that to
save time to automatic builds.

-- 
js
suse labs