From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, idosch@nvidia.com,
petrm@nvidia.com, ecree.xilinx@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ethtool: Monotonically increase the message sequence number
Date: Sat, 13 Jul 2024 22:50:29 +0000 [thread overview]
Message-ID: <172091102996.32137.16513833581251462374.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711080934.2071869-1-danieller@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 11 Jul 2024 11:09:34 +0300 you wrote:
> Currently, during the module firmware flashing process, unicast
> notifications are sent from the kernel using the same sequence number,
> making it impossible for user space to track missed notifications.
>
> Monotonically increase the message sequence number, so the order of
> notifications could be tracked effectively.
>
> [...]
Here is the summary with links:
- [net-next] net: ethtool: Monotonically increase the message sequence number
https://git.kernel.org/netdev/net-next/c/275a63c9fe10
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-13 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 8:09 [PATCH net-next] net: ethtool: Monotonically increase the message sequence number Danielle Ratson
2024-07-11 14:09 ` Petr Machata
2024-07-11 14:23 ` Petr Machata
2024-07-12 0:43 ` Jakub Kicinski
2024-07-13 22:50 ` 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=172091102996.32137.16513833581251462374.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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.