From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
Jamie Gloudon <jamie.gloudon@gmail.com>,
fenghua.yu@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] x86/microcode: Early load microcode
Date: Wed, 12 Dec 2012 09:41:37 -0800 [thread overview]
Message-ID: <50C8C1D1.2000506@zytor.com> (raw)
In-Reply-To: <CACJDEmqNGsigBBktbnptbv3G5VD98F3htfwhx9mVCvz6mRQ0oQ@mail.gmail.com>
On 10/03/2012 06:13 AM, Konrad Rzeszutek Wilk wrote:
> On Tue, Oct 2, 2012 at 3:04 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 10/02/2012 12:00 PM, Konrad Rzeszutek Wilk wrote:
>>>
>>> When he got interrupted did he have any beta patches to dracut that
>>> could be posted?
>>>
>>
>> To *dracut*?
>
> The replacement for mkinitrd. You know the thing that creates your
> initramfs.cpio.gz.
>
Yes... it just seems that mucking with dracut is the last step in the
chain. If your boot loader doesn't support initramfs concatenation, (a)
complain to your bootloader author, (b) you can just use "cat"...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-12-12 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:11 [PATCH 00/11] x86/microcode: Early load microcode Jamie Gloudon
2012-10-01 16:27 ` 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 [this message]
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=50C8C1D1.2000506@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=jamie.gloudon@gmail.com \
--cc=konrad@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.