From: patchwork-bot+netdevbpf@kernel.org
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
kernel@pengutronix.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/1] net: dsa: microchip: ksz9477: export HW stats over stats64 interface
Date: Sat, 19 Feb 2022 19:00:09 +0000 [thread overview]
Message-ID: <164529720998.31615.18049890364706478684.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220219082630.2454948-1-o.rempel@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 19 Feb 2022 09:26:30 +0100 you wrote:
> Provide access to HW offloaded packets over stats64 interface.
> The rx/tx_bytes values needed some fixing since HW is accounting size of
> the Ethernet frame together with FCS.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> changes v4:
> - do not copy raw counters to the stack
> changes v3:
> - move dev->dev_ops->r_mib_stat64 insight of the mutex
> changes v2:
> - fix locking issue in in atomic context
>
> [...]
Here is the summary with links:
- [net-next,v4,1/1] net: dsa: microchip: ksz9477: export HW stats over stats64 interface
https://git.kernel.org/netdev/net-next/c/a7f4f13a0a68
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:[~2022-02-19 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 8:26 [PATCH net-next v4 1/1] net: dsa: microchip: ksz9477: export HW stats over stats64 interface Oleksij Rempel
2022-02-19 9:46 ` Vladimir Oltean
2022-02-19 19: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=164529720998.31615.18049890364706478684.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox