From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, vadim.fedorenko@linux.dev,
kory.maincent@bootlin.com, jacob.e.keller@intel.com, nm@ti.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ethernet: ti: netcp: Use u64_stats_t with u64_stats_sync properly
Date: Tue, 27 Jan 2026 05:10:07 +0000 [thread overview]
Message-ID: <176949060734.690573.3564112889209838707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123164841.2890054-1-mmyangfl@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 24 Jan 2026 00:48:36 +0800 you wrote:
> On 64bit arches, struct u64_stats_sync is empty and provides no help
> against load/store tearing. Convert to u64_stats_t to ensure atomic
> operations.
>
> Note that does not mean the code is now tear-free: there're u32 counters
> unprotected by u64_stats or anything else.
>
> [...]
Here is the summary with links:
- [net-next] net: ethernet: ti: netcp: Use u64_stats_t with u64_stats_sync properly
https://git.kernel.org/netdev/net-next/c/3eef6c061f97
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:[~2026-01-27 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 16:48 [PATCH net-next] net: ethernet: ti: netcp: Use u64_stats_t with u64_stats_sync properly David Yang
2026-01-27 5:10 ` 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=176949060734.690573.3564112889209838707.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox