All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Jaswinder Singh Rajput <jaswinder@infradead.org>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: setup.c fix style problems
Date: Tue, 6 Jan 2009 13:18:02 +0100	[thread overview]
Message-ID: <20090106121802.GA7071@elte.hu> (raw)
In-Reply-To: <3f9a31f40901060207j24c580cfl1e8bc71ae486a4b9@mail.gmail.com>


* Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:

> On Sun, Jan 4, 2009 at 10:51 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > the x86-local declarations in smp.h should probably be moved into a
> > separate smp_x86.h file - to avoid such trouble.
> >
> 
> I think we do not need to make any new files only thing we need is to
> rearrange stuff between existing files.
> 
> Currently there is no such protocol, If we follow this logic then it
> will very easy for us to maintain things:
> 
> CONFIG_SMP -> asm/smp.h
> CONFIG_X86_LOCAL_APIC -> asm/apic.h
> CONFIG_X86_IO_APIC -> asm/io_apic.h

yep.

> And if you want then I will give strict instructions so that we will 
> never face these problems again, like :-
> 
> asm/smp.h:
> 
> #ifndef CONFIG_SMP
> #error "Including wrong file, why you need smp.h for Uniprocessor"
> #else
> ...
> #endif
> 
> Similarly for asm/apic.h and asm/io_apic.h

the smp.h change would work, agreed - but it's not really good for things 
like apic.h and io_apic.h - often apic.h is included to pick up init and 
various callback prototypes - which exist on !CONFIG_X96_IO_APIC too.

	Ingo

      reply	other threads:[~2009-01-06 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 11:01 [PATCH -tip] x86: setup.c fix style problems Jaswinder Singh Rajput
2009-01-04 17:21 ` Ingo Molnar
2009-01-04 17:27   ` Jaswinder Singh Rajput
2009-01-04 17:57   ` Jaswinder Singh Rajput
2009-01-04 20:34     ` Ingo Molnar
2009-01-05  5:04       ` Jaswinder Singh Rajput
2009-01-05 13:15         ` Ingo Molnar
2009-01-05 13:22           ` Jaswinder Singh Rajput
2009-01-05 13:50             ` Ingo Molnar
2009-01-05 14:03               ` Jaswinder Singh Rajput
2009-01-06 10:07   ` Jaswinder Singh Rajput
2009-01-06 12:18     ` Ingo Molnar [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=20090106121802.GA7071@elte.hu \
    --to=mingo@elte.hu \
    --cc=jaswinder@infradead.org \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.