From: patchwork-bot+netdevbpf@kernel.org
To: Andre Przywara <andre.przywara@arm.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, wens@csie.org, samuel@sholland.org,
jernej.skrabec@gmail.com, clabbe.montjoie@gmail.com,
paulk@sys-base.io, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH net-next] net: stmmac: sun8i: drop unneeded default syscon value
Date: Thu, 28 Aug 2025 00:50:06 +0000 [thread overview]
Message-ID: <175634220652.891202.7808539694253002110.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250825172055.19794-1-andre.przywara@arm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 25 Aug 2025 18:20:55 +0100 you wrote:
> For some odd reason we were very jealous about the value of the EMAC
> clock register from the syscon block, insisting on a reset value and
> only doing read-modify-write operations on that register, even though we
> pretty much know the register layout.
> This already led to a basically redundant entry for the H6, which only
> differs by that value. We seem to have the same situation with the new
> A523 SoC, which again is compatible to the A64, but has a different
> syscon reset value.
>
> [...]
Here is the summary with links:
- [net-next] net: stmmac: sun8i: drop unneeded default syscon value
https://git.kernel.org/netdev/net-next/c/330355191a2d
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-28 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 17:20 Andre Przywara
2025-08-27 22:13 ` Jacob Keller
2025-08-28 0:50 ` 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=175634220652.891202.7808539694253002110.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andre.przywara@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jernej.skrabec@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulk@sys-base.io \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
/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
all inboxes | Powered by JetHome®