From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, amcohen@nvidia.com,
idosch@nvidia.com, linux-kselftest@vger.kernel.org,
shuah@kernel.org, mlxsw@nvidia.com
Subject: Re: [PATCH net-next] selftests: mlxsw: rtnetlink: Use devlink_reload() API
Date: Fri, 04 Oct 2024 00:00:33 +0000 [thread overview]
Message-ID: <172800003328.2035955.3929073643835744782.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <844509e3057b65277a7181a23c95b71ec95e8a56.1727706741.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Sep 2024 17:12:50 +0200 you wrote:
> From: Amit Cohen <amcohen@nvidia.com>
>
> The test runs "devlink reload" explicitly. Instead, it is better to use
> devlink_reload() which waits for udev events to be processed. Do not sleep
> after reload, as devlink_reload() blocks until all the netdevs are renamed.
>
> Signed-off-by: Amit Cohen <amcohen@nvidia.com>
> Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> Signed-off-by: Petr Machata <petrm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next] selftests: mlxsw: rtnetlink: Use devlink_reload() API
https://git.kernel.org/netdev/net-next/c/be4e32354457
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-04 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 15:12 [PATCH net-next] selftests: mlxsw: rtnetlink: Use devlink_reload() API Petr Machata
2024-10-04 0:00 ` 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=172800003328.2035955.3929073643835744782.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--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