linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-firmware@kernel.org, jwboyer@kernel.org
Subject: Re: [PATCH 00/15] Misc fixes, sanity checks and xz/zstd compression
Date: Tue, 28 Feb 2023 17:02:05 +0000	[thread overview]
Message-ID: <CACvgo52_rV-CgC4z4S2O98VOMOY-4=A011dBsGJB8+0_bdgDgg@mail.gmail.com> (raw)
In-Reply-To: <c50231609fb4597a1443fbc2dec46fce4589d0eb.camel@infradead.org>

On Tue, 28 Feb 2023 at 16:48, David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Tue, 2023-02-28 at 16:46 +0000, Emil Velikov wrote:
> >
> > Greetings David
> >
> > Don't think I follow - the series is completely unrelated to microcode
> > loading. There isn't any mention of microcode in there, so I'm not
> > sure what inspired the question. Perhaps it was meant for another
> > thread?
>
> cf. https://bugzilla.redhat.com/show_bug.cgi?id=2122271

Nor really a RH/Fedora person, so the link is appreciated.

On my Arch machines, only the AMD PSP firmware is included in the
(mkinitcpio) generated init ramdisk. And as outlined in the bug that
works just fine. Will have a look into this.
Mind you - nearly all the patches can be applied independently of one
another. So dropping the final patch is one option in the short term.

Thanks again,
Emil

  reply	other threads:[~2023-02-28 17:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 18:46 [PATCH 00/15] Misc fixes, sanity checks and xz/zstd compression Emil Velikov
2023-02-18 18:46 ` [PATCH 01/15] WHENCE: remove trailing white space Emil Velikov
2023-02-18 18:46 ` [PATCH 02/15] WHENCE: remove unnecessary filename quotation Emil Velikov
2023-02-18 18:46 ` [PATCH 03/15] check_whence, WHENCE, copy-firmware: escape filenames with spaces Emil Velikov
2023-02-18 18:46 ` [PATCH 04/15] WHENCE: remove duplicate File entries Emil Velikov
2023-02-18 18:46 ` [PATCH 05/15] check_whence: error on duplicate file entries Emil Velikov
2023-02-18 18:46 ` [PATCH 06/15] check_whence: error on directory listed as File Emil Velikov
2023-02-18 18:46 ` [PATCH 07/15] copy-firmware: remove non-applicable file presence test Emil Velikov
2023-02-18 18:46 ` [PATCH 08/15] check_whence: error if File: is actually a link Emil Velikov
2023-02-18 18:46 ` [PATCH 09/15] check_whence: error if symlinks are in-tree Emil Velikov
2023-02-18 18:46 ` [PATCH 10/15] copy-firmware: remove unreachable symlink workarounds Emil Velikov
2023-02-18 18:46 ` [PATCH 11/15] copy-firmware: quote deskdir to prevent word splitting Emil Velikov
2023-02-18 18:46 ` [PATCH 12/15] copy-firmware: tweak sed invocation Emil Velikov
2023-02-18 18:46 ` [PATCH 13/15] copy-firmware: quote the output of dirname Emil Velikov
2023-02-18 18:46 ` [PATCH 14/15] copy-firmware: silence the last shellcheck warnings Emil Velikov
2023-02-18 18:46 ` [PATCH 15/15] Makefile, copy-firmware: support xz/zstd compressed firmware Emil Velikov
2023-02-28 14:18 ` [PATCH 00/15] Misc fixes, sanity checks and xz/zstd compression Emil Velikov
2023-02-28 14:36   ` David Woodhouse
2023-02-28 16:46     ` Emil Velikov
2023-02-28 16:48       ` David Woodhouse
2023-02-28 17:02         ` Emil Velikov [this message]
2023-02-28 17:03           ` David Woodhouse
2023-02-28 17:20             ` Emil Velikov

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='CACvgo52_rV-CgC4z4S2O98VOMOY-4=A011dBsGJB8+0_bdgDgg@mail.gmail.com' \
    --to=emil.l.velikov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@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).