public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Russ Weight <russ.weight@linux.dev>,
	 Danilo Krummrich	 <dakr@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Shuah Khan <shuah@kernel.org>
Cc: Michal Grzedzicki <mge@meta.com>,
	driver-core@lists.linux.dev,  linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v5 0/2] firmware_loader: allow firmware_class.path to take multiple paths
Date: Mon, 23 Mar 2026 10:45:00 -0400	[thread overview]
Message-ID: <ab54ccd1948046e67bb60aec9c9bd0c988d11b36.camel@kernel.org> (raw)
In-Reply-To: <20260323-fw-path-v5-0-e88b2fe145f3@kernel.org>

Erm, obviously I forgot to update the subject line on the b4 cover
letter. Just pretend it says:

    "firmware_loader: add search= module option for multi-path firmware
lookup"

Thanks,
Jeff

On Mon, 2026-03-23 at 10:39 -0400, Jeff Layton wrote:
> This is something Michal had asked for last year, and I just got around
> to implementing. This version also adds some selftests for this
> functionality.
> 
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> Changes in v5:
> - Increase search= string length from 256 to 4096
> - Preprocess search= path when it's set rather than on every firmware load
> - Add selftests for search= functionality
> - Link to v4: https://lore.kernel.org/r/20260320-fw-path-v4-1-7547e2f0dc64@kernel.org
> 
> Changes in v4:
> - Move search path to new search= option that is tried after path=
> - Link to v3: https://lore.kernel.org/r/20260318-fw-path-v3-1-a701a08bc025@kernel.org
> 
> Changes in v3:
> - Allow '\' to escape a literal ':' or '\' in the string
> - Link to v2: https://lore.kernel.org/r/20260318-fw-path-v2-1-8a106eb91eb4@kernel.org
> 
> Changes in v2:
> - switch to using ':' as path delimiter
> - Link to v1: https://lore.kernel.org/r/20260318-fw-path-v1-1-7884d9bf618f@kernel.org
> 
> ---
> Jeff Layton (2):
>       firmware_loader: add search= module option for multi-path firmware lookup
>       selftests/firmware: add search path test for firmware_class.search=
> 
>  drivers/base/firmware_loader/main.c           | 273 +++++++++++++++++++-------
>  tools/testing/selftests/firmware/Makefile     |   2 +-
>  tools/testing/selftests/firmware/fw_search.sh | 222 +++++++++++++++++++++
>  3 files changed, 420 insertions(+), 77 deletions(-)
> ---
> base-commit: c369299895a591d96745d6492d4888259b004a9e
> change-id: 20260317-fw-path-a094c30259a5
> 
> Best regards,

-- 
Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2026-03-23 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 14:39 [PATCH v5 0/2] firmware_loader: allow firmware_class.path to take multiple paths Jeff Layton
2026-03-23 14:39 ` [PATCH v5 1/2] firmware_loader: add search= module option for multi-path firmware lookup Jeff Layton
2026-03-23 14:39 ` [PATCH v5 2/2] selftests/firmware: add search path test for firmware_class.search= Jeff Layton
2026-03-23 14:45 ` Jeff Layton [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=ab54ccd1948046e67bb60aec9c9bd0c988d11b36.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mge@meta.com \
    --cc=rafael@kernel.org \
    --cc=russ.weight@linux.dev \
    --cc=shuah@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