From: Jaswinder Singh Rajput <jaswinder@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
"H. Peter Anvin" <hpa@kernel.org>,
tigran@aivazian.fsnet.co.uk, shaohua.li@intel.com,
rusty@rustcorp.com.au, Andi Kleen <andi@firstfloor.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PULL -tip] x86: fix style problems in microcode_intel.c, msr.c and module_XX.c
Date: Mon, 12 Jan 2009 18:21:17 +0530 [thread overview]
Message-ID: <1231764677.10461.8.camel@jaswinder.satnam> (raw)
In-Reply-To: <20090112104429.GE10405@elte.hu>
On Mon, 2009-01-12 at 11:44 +0100, Ingo Molnar wrote:
> * Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:
>
> > On Mon, Jan 12, 2009 at 3:50 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > hm, are the mpparse.c structural cleanups that i suggested some time ago
> > > still on your list? I think the functions replace_intsrc_all(),
> > > smp_scan_config() and smp_read_mpc() need those cleanups.
> > >
> >
> > Yes, it is still in my TODO list. But before that I need to submit
> > patches to get some extra space:
> > 0001-x86-replacing-mp_config_ioapic-with-mpc_ioapic.patch
> > 0002-x86-replacing-mp_config_intsrc-with-mpc_intsrc.patch
> >
> > And then I will make final changes in mpparse.c
>
> ok.
>
I send [PULL -tip] x86: replacing mp_config_X with mpc_X which
includes:
x86: replacing mp_config_ioapic with mpc_ioapic
x86: replacing mp_config_intsrc with mpc_intsrc
--
JSR
next prev parent reply other threads:[~2009-01-12 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 9:39 [PULL -tip] x86: fix style problems in microcode_intel.c, msr.c and module_XX.c Jaswinder Singh Rajput
2009-01-12 10:20 ` Ingo Molnar
2009-01-12 10:43 ` Jaswinder Singh Rajput
2009-01-12 10:44 ` Ingo Molnar
2009-01-12 12:51 ` Jaswinder Singh Rajput [this message]
2009-01-12 10: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=1231764677.10461.8.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=andi@firstfloor.org \
--cc=hpa@kernel.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=shaohua.li@intel.com \
--cc=tigran@aivazian.fsnet.co.uk \
--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