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 22:40:45 +0100	[thread overview]
Message-ID: <20090107214045.GA15761@elte.hu> (raw)
In-Reply-To: <3f9a31f40901071043u5a112962l2dd7e1d88de8aae2@mail.gmail.com>


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

> On Wed, Jan 7, 2009 at 11:05 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Jaswinder Singh Rajput <jaswinder@infradead.org> wrote:
> >
> >> I send new 4 patches:
> >>
> >> [PATCH -tip 1/4 V2] x86: smp.h move stack_processor_id declartion to cpu.h
> >> [PATCH -tip 2/4 V2] x86: smp.h move safe_smp_processor_id declartion to cpu.h
> >> [PATCH -tip 3/4 V2] x86: smp.h move cpu_physical_id declartion to cpu.h
> >> [PATCH -tip 4/4 V2] x86: smp.h move boot_cpu_id declartion to cpu.h
> >>
> >> Please accept them.
> >
> > Just to make sure: they should solve the 3 failures i reported?
> >
> 
> Yes.

ok, i've applied the remaining bits and they are holding up quite well so 
far in tip/master testing:

6d652ea: x86: smp.h move boot_cpu_id declartion to cpu.h
af8968a: x86: smp.h move cpu_physical_id declartion to cpu.h
96b89dc: x86: smp.h move safe_smp_processor_id declartion to cpu.h
f472cdb: x86: smp.h move stack_processor_id declartion to cpu.h

	Ingo

	Ingo

      parent reply	other threads:[~2009-01-07 21:41 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
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 [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=20090107214045.GA15761@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