All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: [PATCH net-next 03/11] nfp: use PCI_DEVICE_ID_NETRONOME_NFP6000_VF for VFs instead
Date: Fri, 11 Mar 2022 11:42:58 +0100	[thread overview]
Message-ID: <20220311104306.28357-4-simon.horman@corigine.com> (raw)
In-Reply-To: <20220311104306.28357-1-simon.horman@corigine.com>

From: Dirk van der Merwe <dirk.vandermerwe@netronome.com>

The PCI_DEVICE_ID_NETRONOME_NFP6000_VF is available for use and
should be used instead of the PCI_DEVICE_NFP6000VF. Meanwhile,
PCI_DEVICE_NFP6000VF PCI ID is removed for not being used.

Signed-off-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Signed-off-by: Fei Qin <fei.qin@corigine.com>
Signed-off-by: Simon Horman <simon.horman@corigine.com>
---
 drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c b/drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c
index 87f2268b16d6..694152016b25 100644
--- a/drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c
+++ b/drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c
@@ -36,9 +36,8 @@ struct nfp_net_vf {
 
 static const char nfp_net_driver_name[] = "nfp_netvf";
 
-#define PCI_DEVICE_NFP6000VF		0x6003
 static const struct pci_device_id nfp_netvf_pci_device_ids[] = {
-	{ PCI_VENDOR_ID_NETRONOME, PCI_DEVICE_NFP6000VF,
+	{ PCI_VENDOR_ID_NETRONOME, PCI_DEVICE_ID_NETRONOME_NFP6000_VF,
 	  PCI_VENDOR_ID_NETRONOME, PCI_ANY_ID,
 	  PCI_ANY_ID, 0,
 	},
-- 
2.30.2


  parent reply	other threads:[~2022-03-11 10:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 10:42 [PATCH net-next 0/11] nfp: preliminary support for NFP-3800 Simon Horman
2022-03-11 10:42 ` [PATCH net-next 01/11] nfp: remove defines for unused control bits Simon Horman
2022-03-11 10:42 ` [PATCH net-next 02/11] nfp: remove pessimistic NFP_QCP_MAX_ADD limits Simon Horman
2022-03-11 10:42 ` Simon Horman [this message]
2022-03-11 10:42 ` [PATCH net-next 04/11] nfp: use PluDevice register for model for non-NFP6000 chips Simon Horman
2022-03-11 10:43 ` [PATCH net-next 05/11] nfp: sort the device ID tables Simon Horman
2022-03-11 10:43 ` [PATCH net-next 06/11] nfp: introduce dev_info static chip data Simon Horman
2022-03-11 10:43 ` [PATCH net-next 07/11] nfp: use dev_info for PCIe config space BAR offsets Simon Horman
2022-03-11 10:43 ` [PATCH net-next 08/11] nfp: use dev_info for the DMA mask Simon Horman
2022-03-11 10:43 ` [PATCH net-next 09/11] nfp: parametrize QCP offset/size using dev_info Simon Horman
2022-03-11 10:43 ` [PATCH net-next 10/11] nfp: take chip version into account for ring sizes Simon Horman
2022-03-11 10:43 ` [PATCH net-next 11/11] nfp: add support for NFP3800/NFP3803 PCIe devices Simon Horman
2022-03-12  7:40 ` [PATCH net-next 0/11] nfp: preliminary support for NFP-3800 patchwork-bot+netdevbpf

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=20220311104306.28357-4-simon.horman@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.