Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models

[Vinod Koul <vinod.koul@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

On Wed, Jul 27, 2016 at 03:22:21PM +0100, Mark Brown wrote:
> On Wed, Jul 27, 2016 at 06:27:51PM +0530, Vinod Koul wrote:
> > On Wed, Jul 27, 2016 at 09:53:24AM +0200, Arnd Bergmann wrote:
> 
> > > We should be at the point where an 'allmodconfig' build on ARM
> > > gets you most of the drivers and builds without warnings (using
> > > gcc-4.9 or higher).
> 
> > The problem is drivers depend on various ARM sub arch's. That is the
> > sole reason why I have multiple configs now.
> 
> That shouldn't be the case at least for any new code, things should at
> least build OK with an || COMPILE_TEST normally.  Old code may need
> fixing up for this.

That's right, this is problematic mostly with older code and for ARMv5 and
below. As I said later code & sub-ARCHs seems to be well covered with
current multi-vx-configs...

> > Which brings me to another problem :-) why should individual drivers
> > depend on ARM sub arch's. Depends on ARM, yes. First look at code tells
> > me they shouldn't!, probably sometime back that was true, but I don't
> > think that should be the case now, ofcourse you would know better!
> 
> The dependencies are there to improve UX when people are configuring
> their kernels - it stops them being asked about hardware they can't
> possibly have in their system.  If there's no build time reason for it
> then it should be (ARCH_FOO || COMPILE_TEST) so people can do build
> tests.

That is a valid point as well. This seems better suggestion to me.

-- 
~Vinod

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]