From: patchwork-bot+netdevbpf@kernel.org
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] net: mvneta: Armada 98DX2530 SoC
Date: Thu, 17 Mar 2022 10:10:10 +0000 [thread overview]
Message-ID: <164751181021.10384.6185526581828131470.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220315215207.2746793-1-chris.packham@alliedtelesis.co.nz>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 16 Mar 2022 10:52:05 +1300 you wrote:
> This is split off from [1] to let it go in via net-next rather than waiting for
> the rest of the series to land.
>
> [1] - https://lore.kernel.org/lkml/20220314213143.2404162-1-chris.packham@alliedtelesis.co.nz/
>
> Chris Packham (2):
> dt-bindings: net: mvneta: Add marvell,armada-ac5-neta
> net: mvneta: Add support for 98DX2530 Ethernet port
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] dt-bindings: net: mvneta: Add marvell,armada-ac5-neta
https://git.kernel.org/netdev/net-next/c/270a95966881
- [net-next,v4,2/2] net: mvneta: Add support for 98DX2530 Ethernet port
https://git.kernel.org/netdev/net-next/c/2d2a514c1d61
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-03-17 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 21:52 [PATCH net-next v4 0/2] net: mvneta: Armada 98DX2530 SoC Chris Packham
2022-03-15 21:52 ` [PATCH net-next v4 1/2] dt-bindings: net: mvneta: Add marvell,armada-ac5-neta Chris Packham
2022-03-15 21:52 ` [PATCH net-next v4 2/2] net: mvneta: Add support for 98DX2530 Ethernet port Chris Packham
2022-03-17 10: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=164751181021.10384.6185526581828131470.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).