From: Luis Chamberlain <mcgrof@kernel.org>
To: David Airlie <airlied@redhat.com>
Cc: Dave Airlie <airlied@gmail.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modules/firmware: add a new option to denote a firmware group to choose one.
Date: Tue, 23 May 2023 22:40:03 -0700 [thread overview]
Message-ID: <ZG2jMx3yo8sHK7Bc@bombadil.infradead.org> (raw)
In-Reply-To: <CAMwc25poqP-S2DSXLZuRA7F20fHsiq7uACbxUvYHCEkpY7BoHA@mail.gmail.com>
On Wed, May 24, 2023 at 03:35:41PM +1000, David Airlie wrote:
> On Wed, May 24, 2023 at 3:26 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > Hey Dave, just curious if there was going to be another follow up patch
> > for this or if it was already posted. I don't see it clearly so just
> > wanted to double check.
>
> I'm still considering the options here.
>
> I could leave the kernel patch as-is and add explicit sorting in
> dracut for anything in the groups, but then we have to name/version
> the firmware in a certain way, another option might be to emit the
> group bounds and two records, one old, one new per-fw file, then have
> some sort of explicit versioning by the driver over what order to load
> them.
Great thanks, just wanted to make sure I didn't neglect any pending
patch.
Luis
prev parent reply other threads:[~2023-05-24 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 4:36 [PATCH] modules/firmware: add a new option to denote a firmware group to choose one Dave Airlie
2023-04-20 19:09 ` Lucas De Marchi
2023-04-24 5:44 ` Dave Airlie
2023-04-24 17:01 ` Lucas De Marchi
2023-04-24 22:56 ` Luis Chamberlain
2023-05-02 18:11 ` Lucas De Marchi
2023-05-02 22:10 ` Luis Chamberlain
2023-05-03 3:19 ` Dave Airlie
2023-05-24 5:26 ` Luis Chamberlain
2023-05-24 5:35 ` David Airlie
2023-05-24 5:40 ` Luis Chamberlain [this message]
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=ZG2jMx3yo8sHK7Bc@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@intel.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 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).