All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Gabriel C <nix.or.die@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Builtin microcode does nothing..
Date: Sat, 21 May 2016 09:45:58 +0200	[thread overview]
Message-ID: <20160521074558.GA8293@pd.tnic> (raw)
In-Reply-To: <323291d3-64ae-4648-a731-e695dab2df04@gmail.com>

On Sat, May 21, 2016 at 02:20:56AM +0200, Gabriel C wrote:
> I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way
> does work.

Good, this confirms what I've been debugging here too.

Thanks.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

  parent reply	other threads:[~2016-05-21  7:46 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
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 [this message]
     [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=20160521074558.GA8293@pd.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@gmail.com \
    /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.