On Tue, Oct 16, 2012 at 12:18:05AM +0200, Frederic Weisbecker wrote: > 2012/10/15 Arnd Bergmann <a...@arndb.de>: > > On Monday 15 October 2012, Steven Rostedt wrote: > >> On Mon, 2012-10-15 at 22:23 +0200, Frederic Weisbecker wrote: > >> > 2012/10/15 Steven Rostedt <rost...@goodmis.org>: > >> > > On Mon, 2012-10-15 at 17:11 +0100, Catalin Marinas wrote:
> >> > > BTW, is there any rational reason that the include path lookup doesn't > >> > > just check for the files in include/asm-generic after looking in > >> > > arch/*/include/asm? > >> > > Really, the best way would be just to add the default asm files into > >> > > include/asm-generic and be done with it. I hate the fact that we need > >> > > to > >> > > touch every arch for every generic default file. > >> > Agreed. I'm including Arnd in the conversation. > >> As David Howells is doing user space header work, I'll include him too. > >> Maybe someone can shed some light onto this. I'll just add my vote there, I've *no* idea why asm-generic isn't in the include path by default, I could never figure out what that was for. > > A number of people have expressed the wish to do this through Makefile > > magic, but > > so far nobody has been able to come up with the right incantation. > > > > I've spent a day trying to figure it out, and I think Mark Brown tried some > > of > > the same things. It's probably not all that hard for someone who is more > > familiar > > with the Kbuild internals. I came up with stuff for it, though it needed prettyfying. > This seems to do the trick: > (It's the diff result of ln -s asm-generic include/asm) That'd work, but I assume there is some reason why we've got this system of explicitly adding each file. It's not like cpp can test for the presence of include files. If we can't figure out why we're not doing this I'd propose we start. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
