From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
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: Thu, 8 Jan 2009 00:13:19 +0530 [thread overview]
Message-ID: <3f9a31f40901071043u5a112962l2dd7e1d88de8aae2@mail.gmail.com> (raw)
In-Reply-To: <20090107173509.GD24982@elte.hu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 775 bytes --]
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.
I am sorry for earlier errors messages.
Thanks--JSRÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-01-07 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 11:56 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 [this message]
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=3f9a31f40901071043u5a112962l2dd7e1d88de8aae2@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jaswinder@infradead.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®