From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?=C3=81lvaro_Fern=C3=A1ndez_Rojas_=3Cnoltari=40gmail=2Ecom=3E?=@ci.codeaurora.org
Cc: jonas.gorski@gmail.com, davem@davemloft.net, kuba@kernel.org,
robh+dt@kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: mdio: Add BCM6368 MDIO mux bus controller
Date: Tue, 16 Mar 2021 19:00:07 +0000 [thread overview]
Message-ID: <161592120798.24247.13693268552230553993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210315154528.30212-1-noltari@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 15 Mar 2021 16:45:26 +0100 you wrote:
> This controller is present on BCM6318, BCM6328, BCM6362, BCM6368 and BCM63268
> SoCs.
>
> v2: add changes suggested by Andrew Lunn and Jakub Kicinski.
>
> Álvaro Fernández Rojas (2):
> dt-bindings: net: Add bcm6368-mdio-mux bindings
> net: mdio: Add BCM6368 MDIO mux bus controller
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] dt-bindings: net: Add bcm6368-mdio-mux bindings
https://git.kernel.org/netdev/net-next/c/da6557edb9f3
- [v2,net-next,2/2] net: mdio: Add BCM6368 MDIO mux bus controller
https://git.kernel.org/netdev/net-next/c/e239756717b5
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:[~2021-03-16 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:45 [PATCH v2 net-next 0/2] net: mdio: Add BCM6368 MDIO mux bus controller Álvaro Fernández Rojas
2021-03-15 15:45 ` [PATCH v2 net-next 1/2] dt-bindings: net: Add bcm6368-mdio-mux bindings Álvaro Fernández Rojas
2021-03-15 15:45 ` [PATCH v2 net-next 2/2] net: mdio: Add BCM6368 MDIO mux bus controller Álvaro Fernández Rojas
2021-03-16 19: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=161592120798.24247.13693268552230553993.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?=C3=81lvaro_Fern=C3=A1ndez_Rojas_=3Cnoltari=40gmail=2Ecom=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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).