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, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, horatiu.vultur@microchip.com,
UNGLinuxDriver@microchip.com, p.zabel@pengutronix.de,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: lan966x: make reset optional
Date: Fri, 02 Sep 2022 11:30:17 +0000 [thread overview]
Message-ID: <166211821772.29115.1067348886284578708.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220831111855.1749646-1-michael@walle.cc>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 31 Aug 2022 13:18:53 +0200 you wrote:
> This is the remaining part of the reset rework on the LAN966x targetting
> the netdev tree.
>
> The former series can be found at:
> https://lore.kernel.org/lkml/20220826115607.1148489-1-michael@walle.cc/
>
> Michael Walle (2):
> dt-bindings: net: sparx5: don't require a reset line
> net: lan966x: make reset optional
>
> [...]
Here is the summary with links:
- [net-next,1/2] dt-bindings: net: sparx5: don't require a reset line
https://git.kernel.org/netdev/net-next/c/baa6a9b59070
- [net-next,2/2] net: lan966x: make reset optional
https://git.kernel.org/netdev/net-next/c/f4c1f51cea4e
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-09-02 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:18 [PATCH net-next 0/2] net: lan966x: make reset optional Michael Walle
2022-08-31 11:18 ` [PATCH net-next 1/2] dt-bindings: net: sparx5: don't require a reset line Michael Walle
2022-08-31 11:18 ` [PATCH net-next 2/2] net: lan966x: make reset optional Michael Walle
2022-09-02 11: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=166211821772.29115.1067348886284578708.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--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=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).