From: patchwork-bot+netdevbpf@kernel.org
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: chester62515@gmail.com, alexandre.torgue@foss.st.com,
andrew+netdev@lunn.ch, conor+dt@kernel.org, davem@davemloft.net,
devicetree@vger.kernel.org, edumazet@google.com,
festevam@gmail.com, Frank.Li@nxp.com,
ghennadi.procopciuc@oss.nxp.com, imx@lists.linux.dev,
kuba@kernel.org, jan.petrous@oss.nxp.com, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, mbrugger@suse.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org, s32@nxp.com,
pabeni@redhat.com, kernel@pengutronix.de, robh@kernel.org,
s.hauer@pengutronix.de, linaro-s32@linaro.org
Subject: Re: [PATCH v6 0/3] s32g: Use a syscon for GPR
Date: Thu, 05 Feb 2026 02:30:08 +0000 [thread overview]
Message-ID: <177025860808.131667.13084016124799705995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1769764941.git.dan.carpenter@linaro.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 30 Jan 2026 16:19:35 +0300 you wrote:
> The s32g devices have a GPR register region which holds a number of
> miscellaneous registers. Currently only the stmmac/dwmac-s32.c uses
> anything from there and we just add a line to the device tree to
> access that GMAC_0_CTRL_STS register:
>
> reg = <0x4033c000 0x2000>, /* gmac IP */
> <0x4007c004 0x4>; /* GMAC_0_CTRL_STS */
>
> [...]
Here is the summary with links:
- [v6,1/3] net: stmmac: s32: use a syscon for S32_PHY_INTF_SEL_RGMII
https://git.kernel.org/netdev/net-next/c/b0eeeb1b70c0
- [v6,2/3] dt-bindings: net: nxp,s32-dwmac: Use the GPR syscon
https://git.kernel.org/netdev/net-next/c/0d9588039543
- [v6,3/3] dts: s32g: Add GPR syscon region
(no matching commit)
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-02-05 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 13:19 [PATCH v6 0/3] s32g: Use a syscon for GPR Dan Carpenter
2026-01-30 13:19 ` [PATCH v6 1/3] net: stmmac: s32: use a syscon for S32_PHY_INTF_SEL_RGMII Dan Carpenter
2026-01-30 13:19 ` [PATCH v6 2/3] dt-bindings: net: nxp,s32-dwmac: Use the GPR syscon Dan Carpenter
2026-01-30 13:19 ` [PATCH v6 3/3] dts: s32g: Add GPR syscon region Dan Carpenter
2026-02-03 11:18 ` [PATCH v6 0/3] s32g: Use a syscon for GPR Paolo Abeni
2026-02-03 14:51 ` Dan Carpenter
2026-02-03 22:54 ` Jakub Kicinski
2026-02-04 12:08 ` Dan Carpenter
2026-02-05 2:30 ` 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=177025860808.131667.13084016124799705995.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=jan.petrous@oss.nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linaro-s32@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mbrugger@suse.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.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