From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Peter Oruba" <peter.oruba@amd.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Tigran Aivazian" <tigran@aivazian.fsnet.co.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
"Max Krasnyansky" <maxk@qualcomm.com>
Subject: Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes
Date: Fri, 1 Aug 2008 00:02:27 +0200 [thread overview]
Message-ID: <b647ffbd0807311502i48dbe916l41e417e1e3941160@mail.gmail.com> (raw)
In-Reply-To: <20080731212701.GG2729@elte.hu>
2008/7/31 Ingo Molnar <mingo@elte.hu>:
>
> * Peter Oruba <peter.oruba@amd.com> wrote:
>
>> Fixed coding style issues.
>
> applied to tip/x86/microcode - thanks Peter.
>
> Will you take a shot at moving the driver to early init (and early SMP
> init) code, as suggested by Dmitry?
I have another fix for 'microcode' (one place may race vs.
sched_setaffinity()) and a few ideas/improvements to try. I would also
do this 'move-cpu-hotplug-activities-to-early-init' thing (but
perhaps, not earlier than on Saturday-Sunday) if Peter doesn't come up
with a patch by this time.
btw., is tip/x86/microcode a .27 material? I mean, if I do some work,
should I do it on top of the current linus-git or -tip (or both)?
>
> Ingo
>
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2008-07-31 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 15:41 Peter Oruba
2008-07-29 15:41 ` [patch 1/4] x86: AMD microcode patch loader style corrections Peter Oruba
2008-07-29 15:41 ` [patch 2/4] x86: Intel " Peter Oruba
2008-07-29 15:41 ` [patch 3/4] x86: Moved function declarations out from AMD microcode patch loader to heade file Peter Oruba
2008-07-29 15:41 ` [patch 4/4] x86: Minor pointer type cast in AMD microcode patch loader Peter Oruba
2008-07-29 16:18 ` [patch 0/4] x86: AMD microcode patch loading v2 fixes Dmitry Adamushko
2008-07-29 17:49 ` Max Krasnyansky
2008-07-29 19:37 ` Dmitry Adamushko
2008-07-30 9:28 ` Peter Oruba
2008-07-30 9:57 ` Dmitry Adamushko
2008-07-30 10:34 ` Dmitry Adamushko
2008-07-30 16:35 ` Max Krasnyansky
2008-07-30 18:38 ` Dmitry Adamushko
2008-07-31 21:24 ` Ingo Molnar
2008-08-01 2:23 ` Max Krasnyansky
2008-07-30 16:54 ` Max Krasnyansky
2008-07-30 20:59 ` Dmitry Adamushko
2008-08-01 2:18 ` Max Krasnyansky
2008-08-01 11:25 ` Dmitry Adamushko
2008-08-01 12:21 ` Peter Oruba
2008-08-01 15:26 ` H. Peter Anvin
2008-07-31 21:27 ` Ingo Molnar
2008-07-31 22:02 ` Dmitry Adamushko [this message]
2008-07-31 22:12 ` 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=b647ffbd0807311502i48dbe916l41e417e1e3941160@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=peter.oruba@amd.com \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
/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
Powered by JetHome