From: patchwork-bot+netdevbpf@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, nicolas.ferre@microchip.com,
claudiu.beznea@microchip.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v3 0/5] PolarFire SoC macb reset support
Date: Fri, 08 Jul 2022 03:10:13 +0000 [thread overview]
Message-ID: <165724981392.15320.15228672706280247998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220706095129.828253-1-conor.dooley@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Jul 2022 10:51:24 +0100 you wrote:
> Hey all,
> Jakub requested that these patches be split off from the series
> adding the reset controller itself that I sent ~yesterday~ last
> week [0].
>
> The Cadence MACBs on PolarFire SoC (MPFS) have reset capability and are
> compatible with the zynqmp's init function. I have removed the zynqmp
> specific comments from that function & renamed it to reflect what it
> does, since it is no longer zynqmp only.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] dt-bindings: net: cdns,macb: document polarfire soc's macb
https://git.kernel.org/netdev/net-next/c/b09c6f8ff731
- [net-next,v3,2/5] net: macb: add polarfire soc reset support
https://git.kernel.org/netdev/net-next/c/8aad66aa59be
- [net-next,v3,3/5] net: macb: unify macb_config alignment style
https://git.kernel.org/netdev/net-next/c/649bef9c7663
- [net-next,v3,4/5] net: macb: simplify error paths in init_reset_optional()
https://git.kernel.org/netdev/net-next/c/ea242f821a2d
- [net-next,v3,5/5] net: macb: sort init_reset_optional() with other init()s
https://git.kernel.org/netdev/net-next/c/8a78ac73de20
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:[~2022-07-08 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 9:51 [net-next PATCH v3 0/5] PolarFire SoC macb reset support Conor Dooley
2022-07-06 9:51 ` [net-next PATCH v3 1/5] dt-bindings: net: cdns,macb: document polarfire soc's macb Conor Dooley
2022-07-06 9:51 ` [net-next PATCH v3 2/5] net: macb: add polarfire soc reset support Conor Dooley
2022-07-06 9:51 ` [net-next PATCH v3 3/5] net: macb: unify macb_config alignment style Conor Dooley
2022-07-06 9:51 ` [net-next PATCH v3 4/5] net: macb: simplify error paths in init_reset_optional() Conor Dooley
2022-07-06 9:51 ` [net-next PATCH v3 5/5] net: macb: sort init_reset_optional() with other init()s Conor Dooley
2022-07-08 3: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=165724981392.15320.15228672706280247998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).