From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Palmer <daniel@0x0f.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
denis@h3q.com
Subject: Re: [PATCH] net: i825xx: 82596: use MMIO accessors for the MVME16x PORT/CA registers
Date: Wed, 28 Oct 2026 23:40:05 +0000 [thread overview]
Message-ID: <179323080507.1480461.14843841868832449618.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261025024514.802862-1-daniel@0x0f.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 25 Oct 2026 11:45:14 +0900 you wrote:
> On the MVME16x the two port registers need to be written in order to latch
> the correct 32bit value.
>
> The way the code is currently written means that modern GCC can decide to
> optimize the writes and break that latching.
>
> Convert the MVME16x specific register accesses to use the proper io
> accessors to restore the latching and make the driver functional again.
>
> [...]
Here is the summary with links:
- net: i825xx: 82596: use MMIO accessors for the MVME16x PORT/CA registers
https://git.kernel.org/netdev/net/c/7cceaba6ffbc
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-10-28 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 2:45 [PATCH] net: i825xx: 82596: use MMIO accessors for the MVME16x PORT/CA registers Daniel Palmer
2026-10-25 2:50 ` netdev-bot+sinfo
2026-10-25 2:52 ` Daniel Palmer
2026-10-28 23:40 ` 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=179323080507.1480461.14843841868832449618.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@0x0f.com \
--cc=davem@davemloft.net \
--cc=denis@h3q.com \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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