public inbox for linux-kernel@vger.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>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>,
	James.Bottomley@hansenpartnership.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip 0/7] x86: move NON-SMP data from smp.h
Date: Wed, 7 Jan 2009 16:15:22 +0100	[thread overview]
Message-ID: <20090107151522.GA5341@elte.hu> (raw)
In-Reply-To: <20090107151223.GA4899@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > * Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:
> > 
> > > Hello Ingo,
> > > 
> > > On Wed, Jan 7, 2009 at 7:03 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > > >
> > > > * Ingo Molnar <mingo@elte.hu> wrote:
> > > >
> > > >> applied to tip/x86/cleanups:
> > > >
> > > > excluded it again from tip/master, due to this build failure:
> > > >
> > > 
> > > Please accept only first 4 patches:
> > > 
> > > 1.  x86: smp.h remove obsolete function declaration
> > > 2.  x86: smp.h move zap_low_mappings declartion to tlbflush.h
> > > 3.  x86: smp.h move prefill_possible_map declartion to cpu.h
> > > 4.  x86: smp.h move stack_processor_id declartion to cpu.h
> > > 
> > > Then it will easier for me to to focus on only few things.
> > 
> > ok, i dropped the others.
> 
> i dropped the rest too, due to:
> 
>  arch/x86/kernel/cpu/common.c:983: error: implicit declaration of function 'stack_smp_processor_id'
> 
> config attached. Please resend the whole lot once you have those configs 
> working and if you are reasonably sure similar bugs are not in other 
> places.

note, i kept these:

6e5385d: x86: smp.h move prefill_possible_map declartion to cpu.h
dacf733: x86: smp.h move zap_low_mappings declartion to tlbflush.h
7760ec7: x86: smp.h remove obsolete function declaration

as they seem fairly safe.

	Ingo

  reply	other threads:[~2009-01-07 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 11:56 [PATCH -tip 0/7] x86: move NON-SMP data from smp.h Jaswinder Singh Rajput
2009-01-07 12:51 ` Ingo Molnar
2009-01-07 13:33   ` Ingo Molnar
2009-01-07 13:57     ` Jaswinder Singh Rajput
2009-01-07 15:03       ` Ingo Molnar
2009-01-07 15:12         ` Ingo Molnar
2009-01-07 15:15           ` Ingo Molnar [this message]
2009-01-07 15:19             ` Jaswinder Singh Rajput
2009-01-07 16:12             ` Jaswinder Singh Rajput
2009-01-07 17:35               ` Ingo Molnar
2009-01-07 18:43                 ` Jaswinder Singh Rajput
2009-01-07 18:48                   ` Ingo Molnar
2009-01-07 21:40                   ` Ingo Molnar

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=20090107151522.GA5341@elte.hu \
    --to=mingo@elte.hu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox