On Thursday 17 July 2014 12:38:15 Sam Ravnborg wrote:
> > * We could improve the situation if the definition of this list is
> > changed so we only generate the generic header files that are not
> > already provided by an architecture. If we do this, we can consolidate
> > a lot more here, which is nice, but the cost would be equivalent to
> > another level of indirection and a potential for subtle bugs if it's
> > not done very careful.
> I think this is the way to go - and will try to give it a spin.
>
> Something along these lines:
> include/asm-generic/Kbuild.asm will include a list of all header files
> that shall be present for any architecture and may come from asm-generic.
> If the architecture provide there own file - good.
> If the architecture do not provide their own file => create wrapper.
>
> The arch provided header file comes first in the search path,
> so if a wrapper was generated and later a dedicated file is added
> then we will use the dedicated file and not the wrapper that points
> back to asm-generic.
>
> The same logic applies for uapi/asm-generic as well.
>
> I will try to come up with an implementation of this,
> then we can see if this flys.
Ok, sounds good. Thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
