From: patchwork-bot+netdevbpf@kernel.org
To: Shinas Rasheed <srasheed@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hgani@marvell.com, vimleshk@marvell.com, egallen@redhat.com,
mschmidt@redhat.com, pabeni@redhat.com, horms@kernel.org,
kuba@kernel.org, davem@davemloft.net, wizhao@redhat.com,
konguyen@redhat.com
Subject: Re: [PATCH net-next v2 0/2] support OCTEON CN98 devices
Date: Fri, 01 Dec 2023 07:20:26 +0000 [thread overview]
Message-ID: <170141522689.3845.10892409258943079543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231129045348.2538843-1-srasheed@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Nov 2023 20:53:46 -0800 you wrote:
> Implement device unload control net API required for CN98
> devices and add support in driver for the same.
>
> Changes:
> V2:
> - Changed dev_info print to dev_dbg in device_remove API
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] octeon_ep: implement device unload control net API
https://git.kernel.org/netdev/net-next/c/b77e23f1b03e
- [net-next,v2,2/2] octeon_ep: support OCTEON CN98 devices
https://git.kernel.org/netdev/net-next/c/068b2b649fc1
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:[~2023-12-01 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 4:53 [PATCH net-next v2 0/2] support OCTEON CN98 devices Shinas Rasheed
2023-11-29 4:53 ` [PATCH net-next v2 1/2] octeon_ep: implement device unload control net API Shinas Rasheed
2023-11-29 4:53 ` [PATCH net-next v2 2/2] octeon_ep: support OCTEON CN98 devices Shinas Rasheed
2023-12-01 7:20 ` 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=170141522689.3845.10892409258943079543.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srasheed@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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).