All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, jiri@resnulli.us
Subject: Re: [PATCH net-next] selftests: netdevsim: be less selective for FW for the devlink test
Date: Tue, 27 Feb 2024 14:30:29 +0000	[thread overview]
Message-ID: <170904422998.32001.8138779407658340257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240224050658.930272-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 23 Feb 2024 21:06:58 -0800 you wrote:
> Commit 6151ff9c7521 ("selftests: netdevsim: use suitable existing dummy
> file for flash test") introduced a nice trick to the devlink flashing
> test. Instead of user having to create a file under /lib/firmware
> we just pick the first one that already exists.
> 
> Sadly, in AWS Linux there are no files directly under /lib/firmware,
> only in subdirectories. Don't limit the search to -maxdepth 1.
> We can use the %P print format to get the correct path for files
> inside subdirectories:
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: netdevsim: be less selective for FW for the devlink test
    https://git.kernel.org/netdev/net-next/c/b819a8481a19

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-27 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24  5:06 [PATCH net-next] selftests: netdevsim: be less selective for FW for the devlink test Jakub Kicinski
2024-02-26  9:24 ` Jiri Pirko
2024-02-27 14:30 ` patchwork-bot+netdevbpf [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=170904422998.32001.8138779407658340257.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.