From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jeff@garzik.org, rdreier@cisco.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 net-next] net: ibm: emac: Clear MAL descriptors without memset
Date: Tue, 09 Jun 2026 00:40:11 +0000 [thread overview]
Message-ID: <178096561164.1730160.12681740323501157661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603230754.5535-1-rosenp@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 3 Jun 2026 16:07:53 -0700 you wrote:
> Clear MAL descriptor rings with explicit field stores instead of
> memset(). The descriptor rings are carved from MAL coherent DMA memory,
> which may be mapped uncached on 32-bit powerpc. The optimized memset()
> path can use dcbz there and trigger an alignment warning.
>
> Use WRITE_ONCE() for each field to prevent the compiler from merging
> the stores back into a memset() call.
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next] net: ibm: emac: Clear MAL descriptors without memset
https://git.kernel.org/netdev/net-next/c/f0ba7f385de1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-09 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 23:07 [PATCHv2 net-next] net: ibm: emac: Clear MAL descriptors without memset Rosen Penev
2026-06-09 0:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-03 22:17 Rosen Penev
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=178096561164.1730160.12681740323501157661.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=jeff@garzik.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdreier@cisco.com \
--cc=rosenp@gmail.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