From: patchwork-bot+netdevbpf@kernel.org
To: Michael Walle <michael@walle.cc>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, horatiu.vultur@microchip.com,
UNGLinuxDriver@microchip.com, p.zabel@pengutronix.de,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: lan966x: remove PHY reset support
Date: Sat, 30 Apr 2022 12:30:11 +0000 [thread overview]
Message-ID: <165132181158.22225.4698610186663844622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220428114049.1456382-1-michael@walle.cc>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 28 Apr 2022 13:40:47 +0200 you wrote:
> Remove the unneeded PHY reset node as well as the driver support for it.
>
> This was already discussed [1] and I expect Microchip to Ack on this
> removal. Since there is no user, no breakage is expected.
>
> I'm not sure it this should go through net or net-next and if the patches
> should have a Fixes: tag or not. In upstream linux there was never any user
> of it, so there is no bug to be fixed. But OTOH if the schema fix isn't
> backported, then there might be an older schema version still containing
> the reset node. Thoughts?
>
> [...]
Here is the summary with links:
- [net-next,1/2] dt-bindings: net: lan966x: remove PHY reset
https://git.kernel.org/netdev/net-next/c/4fdabd509df3
- [net-next,2/2] net: lan966x: remove PHY reset support
https://git.kernel.org/netdev/net-next/c/5b06ef86826a
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-30 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 11:40 [PATCH net-next 0/2] net: lan966x: remove PHY reset support Michael Walle
2022-04-28 11:40 ` [PATCH net-next 1/2] dt-bindings: net: lan966x: remove PHY reset Michael Walle
2022-05-03 13:04 ` Rob Herring
2022-05-03 13:22 ` Michael Walle
2022-04-28 11:40 ` [PATCH net-next 2/2] net: lan966x: remove PHY reset support Michael Walle
2022-04-28 20:37 ` [PATCH net-next 0/2] " Horatiu Vultur
2022-04-29 12:45 ` Andrew Lunn
2022-04-30 12: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=165132181158.22225.4698610186663844622.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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