From: Jamie Gloudon <jamie.gloudon@gmail.com>
To: fenghua.yu@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] x86/microcode: Early load microcode
Date: Mon, 1 Oct 2012 12:11:51 -0400 [thread overview]
Message-ID: <20121001161151.GA2640@darkstar> (raw)
Hey,
Any chance of this getting merge for the 3.7 cycle?
Regards,
Jamie Gloudon
next reply other threads:[~2012-10-01 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:11 Jamie Gloudon [this message]
2012-10-01 16:27 ` [PATCH 00/11] x86/microcode: Early load microcode Borislav Petkov
2012-10-01 23:37 ` Jamie Gloudon
2012-10-02 4:39 ` Borislav Petkov
2012-10-02 13:11 ` Jamie Gloudon
2012-10-02 13:46 ` Borislav Petkov
2012-10-02 6:06 ` H. Peter Anvin
2012-10-02 19:00 ` Konrad Rzeszutek Wilk
2012-10-02 19:04 ` H. Peter Anvin
2012-10-03 13:13 ` Konrad Rzeszutek Wilk
2012-12-12 17:41 ` H. Peter Anvin
2012-10-02 19:04 ` Yu, Fenghua
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 8:15 Fenghua Yu
2012-08-20 15:39 ` Borislav Petkov
2012-08-20 15:44 ` Yu, Fenghua
2012-08-20 18:51 ` H. Peter Anvin
2012-08-20 20:04 ` Borislav Petkov
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=20121001161151.GA2640@darkstar \
--to=jamie.gloudon@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).