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, idosch@nvidia.com,
amcohen@nvidia.com, shuah@kernel.org, mlxsw@nvidia.com
Subject: Re: [PATCH net] selftests: forwarding: devlink_lib: Wait for udev events after reloading
Date: Sun, 14 Jul 2024 14:41:35 +0000 [thread overview]
Message-ID: <172096809584.533.3773226039519384629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <89367666e04b38a8993027f1526801ca327ab96a.1720709333.git.petrm@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 11 Jul 2024 17:27:02 +0200 you wrote:
> From: Amit Cohen <amcohen@nvidia.com>
>
> Lately, an additional locking was added by commit c0a40097f0bc
> ("drivers: core: synchronize really_probe() and dev_uevent()"). The
> locking protects dev_uevent() calling. This function is used to send
> messages from the kernel to user space. Uevent messages notify user space
> about changes in device states, such as when a device is added, removed,
> or changed. These messages are used by udev (or other similar user-space
> tools) to apply device-specific rules.
>
> [...]
Here is the summary with links:
- [net] selftests: forwarding: devlink_lib: Wait for udev events after reloading
https://git.kernel.org/netdev/net/c/f67a90a0c8f5
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-07-14 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 15:27 [PATCH net] selftests: forwarding: devlink_lib: Wait for udev events after reloading Petr Machata
2024-07-14 14:41 ` 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=172096809584.533.3773226039519384629.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=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 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.