lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081203121955.GJ6703@one.firstfloor.org>
Date:	Wed, 3 Dec 2008 13:19:55 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Arnd Bergmann <arnd@...db.de>, Andi Kleen <andi@...stfloor.org>,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: New location for generic headers?

> Should we try to get rid of all those silly:
> #include <asm-generic/foo.h>
> files we have in arch/$ARCH/include/asm?
> 
> We could for example add include/generic/ last in the search path.
> Or we could add the files in include/asm and add that last in the
> search path.
> 
> Then if we do not find <asm/foo.h> in arch/$ARCH/include/asm/
> then we search include/asm.

The only problem I see is that it would user space use of asm/ 
without make headers_install impossible. I suppose that could
break the setup of a lot of people? I think it would cause
problems on some of my older boxes at least.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ