From: patchwork-bot+netdevbpf@kernel.org
To: Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzk+dt@kernel.org,
nicolas.ferre@microchip.com, claudiu.beznea@microchip.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, michals@xilinx.com,
harinik@xilinx.com, git@xilinx.com
Subject: Re: [PATCH 0/2] net: macb: Make ZynqMP SGMII phy configuration optional
Date: Fri, 22 Apr 2022 12:00:12 +0000 [thread overview]
Message-ID: <165062881261.32249.18140200057485548714.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1650452590-32948-1-git-send-email-radhey.shyam.pandey@xilinx.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 20 Apr 2022 16:33:08 +0530 you wrote:
> This patchset drop phy-names property from MACB node and also make
> SGMII Phy configuration optional. The motivation for this change
> is to support traditional usescase in which first stage bootloader
> does PS-GT configuration, and should still be supported in macb
> driver.
>
>
> [...]
Here is the summary with links:
- [1/2] dt-bindings: net: cdns,macb: Drop phy-names property for ZynqMP SGMII PHY
https://git.kernel.org/netdev/net-next/c/3ac8316e09b0
- [2/2] net: macb: In ZynqMP initialization make SGMII phy configuration optional
https://git.kernel.org/netdev/net-next/c/29e96fe9e0ec
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-04-22 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:03 Radhey Shyam Pandey
2022-04-20 11:03 ` [PATCH 1/2] dt-bindings: net: cdns,macb: Drop phy-names property for ZynqMP SGMII PHY Radhey Shyam Pandey
2022-04-20 11:03 ` [PATCH 2/2] net: macb: In ZynqMP initialization make SGMII phy configuration optional Radhey Shyam Pandey
2022-04-20 11:17 ` Michal Simek
2022-04-22 12:00 ` 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=165062881261.32249.18140200057485548714.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=harinik@xilinx.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@xilinx.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
all inboxes | Powered by JetHome®