From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@infradead.org>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
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 18:35:09 +0100 [thread overview]
Message-ID: <20090107173509.GD24982@elte.hu> (raw)
In-Reply-To: <1231344766.3770.12.camel@jaswinder.satnam>
* Jaswinder Singh Rajput <jaswinder@infradead.org> wrote:
> On Wed, 2009-01-07 at 16:15 +0100, Ingo Molnar wrote:
> > 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.
>
> 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?
Ingo
next prev parent reply other threads:[~2009-01-07 17:35 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 [this message]
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=20090107173509.GD24982@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