linux-kernel - Re: [PATCH -tip] x86: cpu/cpu.h cleanup

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] [day] [month] [year] [list]

Date:	Sun, 22 Mar 2009 18:35:44 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
cc:	Ingo Molnar <mingo@...e.hu>, x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/cpu.h cleanup

On Sun, 22 Mar 2009, Jaswinder Singh Rajput wrote:
> Is it worth to move arch/x86/kernel/cpu/cpu.h data to asm/cpu.h and if
> required we can also make it private like:
> #ifdef __KERNEL__
> #ifndef MODULE
> private data for kernel only
> #endif
> #endif
> 
> By this way we move header files to include directory. Or you have some
> better option.

There is no option at all. The header files which are in source
directories stay just where they are.

They are there for a reason. Have you even looked which files include
arch/x86/kernel/cpu/cpu.h ?

Thanks,

	tglx
--
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/