From: patchwork-bot+netdevbpf@kernel.org
To: Veerasenareddy Burru <vburru@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v5 0/7] Add octeon_ep driver
Date: Wed, 13 Apr 2022 12:00:13 +0000 [thread overview]
Message-ID: <164985121338.29697.16905786191397026617.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220413033503.3962-1-vburru@marvell.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 12 Apr 2022 20:34:56 -0700 you wrote:
> This driver implements networking functionality of Marvell's Octeon
> PCI Endpoint NIC.
>
> This driver support following devices:
> * Network controller: Cavium, Inc. Device b200
>
> V4 -> V5:
> - Fix warnings reported by clang.
> - Address comments from community reviews.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/7] octeon_ep: Add driver framework and device initialization
https://git.kernel.org/netdev/net-next/c/862cd659a6fb
- [net-next,v5,2/7] octeon_ep: add hardware configuration APIs
https://git.kernel.org/netdev/net-next/c/1f2c2d0cee02
- [net-next,v5,3/7] octeon_ep: Add mailbox for control commands
https://git.kernel.org/netdev/net-next/c/4ca2fbdd0bb6
- [net-next,v5,4/7] octeon_ep: add Tx/Rx ring resource setup and cleanup
https://git.kernel.org/netdev/net-next/c/397dfb57dcc2
- [net-next,v5,5/7] octeon_ep: add support for ndo ops
https://git.kernel.org/netdev/net-next/c/6a610a46bad1
- [net-next,v5,6/7] octeon_ep: add Tx/Rx processing and interrupt support
https://git.kernel.org/netdev/net-next/c/37d79d059606
- [net-next,v5,7/7] octeon_ep: add ethtool support for Octeon PCI Endpoint NIC
https://git.kernel.org/netdev/net-next/c/5cc256e79bff
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-13 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 3:34 [net-next PATCH v5 0/7] Add octeon_ep driver Veerasenareddy Burru
2022-04-13 3:34 ` [net-next PATCH v5 1/7] octeon_ep: Add driver framework and device initialization Veerasenareddy Burru
2022-04-13 8:53 ` Bagas Sanjaya
2022-04-13 9:51 ` Leon Romanovsky
2022-04-13 3:34 ` [net-next PATCH v5 2/7] octeon_ep: add hardware configuration APIs Veerasenareddy Burru
2022-04-13 3:34 ` [net-next PATCH v5 3/7] octeon_ep: Add mailbox for control commands Veerasenareddy Burru
2022-04-13 3:35 ` [net-next PATCH v5 4/7] octeon_ep: add Tx/Rx ring resource setup and cleanup Veerasenareddy Burru
2022-04-13 3:35 ` [net-next PATCH v5 5/7] octeon_ep: add support for ndo ops Veerasenareddy Burru
2022-04-13 3:35 ` [net-next PATCH v5 6/7] octeon_ep: add Tx/Rx processing and interrupt support Veerasenareddy Burru
2022-04-13 3:35 ` [net-next PATCH v5 7/7] octeon_ep: add ethtool support for Octeon PCI Endpoint NIC Veerasenareddy Burru
2022-04-13 12: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=164985121338.29697.16905786191397026617.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vburru@marvell.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).