From: patchwork-bot+netdevbpf@kernel.org
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, alexanderduyck@fb.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, kernel-team@meta.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com, sdf@fomichev.me,
vadim.fedorenko@linux.dev
Subject: Re: [PATCH net 0/2] eth: fbnic: Fix drop stats support
Date: Tue, 05 Aug 2025 23:20:15 +0000 [thread overview]
Message-ID: <175443601574.2197607.15706911174673052016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250802024636.679317-1-mohsin.bashr@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 1 Aug 2025 19:46:34 -0700 you wrote:
> Fix hardware drop stats support on the TX path of fbnic by addressing two
> issues: ensure that tx_dropped stats are correctly copied to the
> rtnl_link_stats64 struct, and protect the copying of drop stats from
> fdb->hw_stats to the local variable with the hw_stats_lock to
> ensure consistency.
>
> Mohsin Bashir (2):
> eth: fbnic: Fix tx_dropped reporting
> eth: fbnic: Lock the tx_dropped update
>
> [...]
Here is the summary with links:
- [net,1/2] eth: fbnic: Fix tx_dropped reporting
https://git.kernel.org/netdev/net/c/2972395d8fad
- [net,2/2] eth: fbnic: Lock the tx_dropped update
https://git.kernel.org/netdev/net/c/53abd9c86fd0
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:[~2025-08-05 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 2:46 [PATCH net 0/2] eth: fbnic: Fix drop stats support Mohsin Bashir
2025-08-02 2:46 ` [PATCH net 1/2] eth: fbnic: Fix tx_dropped reporting Mohsin Bashir
2025-08-04 11:14 ` Simon Horman
2025-08-02 2:46 ` [PATCH net 2/2] eth: fbnic: Lock the tx_dropped update Mohsin Bashir
2025-08-04 11:12 ` Simon Horman
2025-08-05 23:20 ` 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=175443601574.2197607.15706911174673052016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=vadim.fedorenko@linux.dev \
/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.