mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/cpu.h cleanup
Date: Sun, 22 Mar 2009 18:35:44 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.0903221825570.29264@localhost.localdomain> (raw)
In-Reply-To: <1237709776.909.14.camel@localhost.localdomain>

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

      reply	other threads:[~2009-03-22 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22  8:16 Jaswinder Singh Rajput
2009-03-22 17:35 ` Thomas Gleixner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0903221825570.29264@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®