From: patchwork-bot+netdevbpf@kernel.org
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, davem@davemloft.net,
kuba@kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next V1 0/5] net: lan743x: PCI11010 / PCI11414 devices Enhancements
Date: Sun, 13 Feb 2022 12:20:10 +0000 [thread overview]
Message-ID: <164475481083.14254.15796641250627236354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220212155315.340359-1-Raju.Lakkaraju@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 12 Feb 2022 21:23:10 +0530 you wrote:
> This patch series adds support of the Ethernet function of the PCI11010 / PCI11414 devices to the LAN743x driver.
> The PCI1xxxx family of devices consists of a PCIe switch with a variety of embedded PCI endpoints on its downstream ports.
> The PCI11010 / PCI11414 devices include an Ethernet 10/100/1000/2500 function as one of those embedded endpoints.
>
> Raju Lakkaraju (5):
> net: lan743x: Add PCI11010 / PCI11414 device IDs
> net: lan743x: Add support for 4 Tx queues
> net: lan743x: Increase MSI(x) vectors to 16 and Int de-assertion
> timers to 10
> net: lan743x: Add support for SGMII interface
> net: lan743x: Add support for Clause-45 MDIO PHY management
>
> [...]
Here is the summary with links:
- [net-next,V1,1/5] net: lan743x: Add PCI11010 / PCI11414 device IDs
https://git.kernel.org/netdev/net-next/c/bb4f6bffe33c
- [net-next,V1,2/5] net: lan743x: Add support for 4 Tx queues
https://git.kernel.org/netdev/net-next/c/cf9aaea8e55b
- [net-next,V1,3/5] net: lan743x: Increase MSI(x) vectors to 16 and Int de-assertion timers to 10
https://git.kernel.org/netdev/net-next/c/ac16b6eb39d6
- [net-next,V1,4/5] net: lan743x: Add support for SGMII interface
https://git.kernel.org/netdev/net-next/c/a46d9d37c4f4
- [net-next,V1,5/5] net: lan743x: Add support for Clause-45 MDIO PHY management
https://git.kernel.org/netdev/net-next/c/a2ab95a31352
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-02-13 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 15:53 [PATCH net-next V1 0/5] net: lan743x: PCI11010 / PCI11414 devices Enhancements Raju Lakkaraju
2022-02-12 15:53 ` [PATCH net-next V1 1/5] net: lan743x: Add PCI11010 / PCI11414 device IDs Raju Lakkaraju
2022-02-12 15:53 ` [PATCH net-next V1 2/5] net: lan743x: Add support for 4 Tx queues Raju Lakkaraju
2022-02-12 15:53 ` [PATCH net-next V1 3/5] net: lan743x: Increase MSI(x) vectors to 16 and Int de-assertion timers to 10 Raju Lakkaraju
2022-02-12 15:53 ` [PATCH net-next V1 4/5] net: lan743x: Add support for SGMII interface Raju Lakkaraju
2022-02-12 15:53 ` [PATCH net-next V1 5/5] net: lan743x: Add support for Clause-45 MDIO PHY management Raju Lakkaraju
2022-02-12 19:53 ` Andrew Lunn
2022-02-13 12:20 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-15 10:32 [PATCH net-next V1 0/5] net: lan743x: PCI11010 / PCI11414 devices Enhancements Raju Lakkaraju
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=164475481083.14254.15796641250627236354.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.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).