From: Gabriel C <nix.or.die@gmail.com>
To: Borislav Petkov <bp@suse.de>, Jim Bos <jim876@xs4all.nl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Builtin microcode does nothing..
Date: Wed, 25 May 2016 23:29:03 +0200 [thread overview]
Message-ID: <49afc531-e702-5645-ab4b-7086425ecd2e@gmail.com> (raw)
In-Reply-To: <20160525093059.GA3957@pd.tnic>
On 25.05.2016 11:31, Borislav Petkov wrote:
> On Sat, May 21, 2016 at 09:51:18AM +0200, Borislav Petkov wrote:
>> I'll ping you once I'm done testing here.
> Ok, I've just uploaded a branch, it passes testing here.
>
> http://git.kernel.org/cgit/linux/kernel/git/bp/bp.git, branch tip-microcode
I tested your branch on top 4.6 stable.
initrd + buitl-in intel ucode won't boot here. It hangs on grub
'Loading initrd image'..
I'll build an kernel with your patches on my other box later /
tomorrow just to be sure..
I didn't tested without initrd since that worked anyway...
Regards,
Garbiel C
next prev parent reply other threads:[~2016-05-25 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:08 Builtin microcode does nothing Gabriel C
2016-05-20 10:23 ` Borislav Petkov
2016-05-20 16:03 ` Gabriel C
2016-05-21 0:20 ` Gabriel C
2016-05-21 2:59 ` Gabriel C
2016-05-21 7:51 ` Borislav Petkov
2016-05-25 9:31 ` Borislav Petkov
2016-05-25 13:48 ` Jim Bos
2016-05-25 14:57 ` Borislav Petkov
2016-05-25 21:29 ` Gabriel C [this message]
2016-05-25 21:38 ` Borislav Petkov
2016-05-25 21:50 ` Gabriel C
2016-05-25 23:36 ` Gabriel C
2016-05-26 10:03 ` Borislav Petkov
2016-05-26 11:52 ` Gabriel C
2016-05-26 12:46 ` Borislav Petkov
2016-06-03 8:02 ` Borislav Petkov
2016-06-04 0:37 ` Gabriel C
2016-06-04 6:35 ` Borislav Petkov
2016-05-21 7:45 ` Borislav Petkov
[not found] <CAEJqkgjFWak5fUc_zR4v-BDgAnjU0NtRfUDDPaEVGjjbEZoqUQ@mail.gmail.com>
2016-05-20 8:36 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2016-05-20 0:55 Gabriel C
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=49afc531-e702-5645-ab4b-7086425ecd2e@gmail.com \
--to=nix.or.die@gmail.com \
--cc=bp@suse.de \
--cc=jim876@xs4all.nl \
--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