From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
oss-drivers@corigine.com, yu.xiao@corigine.com
Subject: Re: [PATCH net-next 0/2] nfp: support Corigine PCIE vendor ID
Date: Tue, 10 May 2022 01:30:12 +0000 [thread overview]
Message-ID: <165214621292.19985.10851056151206457947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220508173816.476357-1-simon.horman@corigine.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 8 May 2022 19:38:14 +0200 you wrote:
> Historically the nfp driver has supported NFP chips with Netronome's
> PCIE vendor ID. This patch extends the driver to also support NFP
> chips, which at this point are assumed to be otherwise identical from
> a software perspective, that have Corigine's PCIE vendor ID (0x1da8).
>
> This patchset begins by cleaning up strings to make them:
> * Vendor neutral for the NFP chip
> * Relate to Corigine for the driver itself
>
> [...]
Here is the summary with links:
- [net-next,1/2] nfp: vendor neutral strings for chip and Corigne in strings for driver
https://git.kernel.org/netdev/net-next/c/34e244ea1507
- [net-next,2/2] nfp: support Corigine PCIE vendor ID
https://git.kernel.org/netdev/net-next/c/299ba7a32a3c
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-05-10 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 17:38 [PATCH net-next 0/2] nfp: support Corigine PCIE vendor ID Simon Horman
2022-05-08 17:38 ` [PATCH net-next 1/2] nfp: vendor neutral strings for chip and Corigne in strings for driver Simon Horman
2022-05-08 17:38 ` [PATCH net-next 2/2] nfp: support Corigine PCIE vendor ID Simon Horman
2022-05-10 1:30 ` 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=165214621292.19985.10851056151206457947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.com \
--cc=yu.xiao@corigine.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).