From: Michael Margolin <mrgolin@amazon.com>
To: <jgg@nvidia.com>, <leon@kernel.org>, <linux-rdma@vger.kernel.org>
Cc: <sleybo@amazon.com>, <matua@amazon.com>, <gal.pressman@linux.dev>,
"Anas Mousa" <anasmous@amazon.com>
Subject: [PATCH for-next 2/2] RDMA/efa: Add EFA 0xefa4 PCI ID
Date: Sun, 12 Jul 2026 13:44:13 +0000 [thread overview]
Message-ID: <20260712134413.19226-3-mrgolin@amazon.com> (raw)
In-Reply-To: <20260712134413.19226-1-mrgolin@amazon.com>
From: Anas Mousa <anasmous@amazon.com>
Add support for 0xefa4 devices.
Reviewed-by: Michael Margolin <mrgolin@amazon.com>
Signed-off-by: Anas Mousa <anasmous@amazon.com>
---
drivers/infiniband/hw/efa/efa_main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/infiniband/hw/efa/efa_main.c b/drivers/infiniband/hw/efa/efa_main.c
index 97da8e828e34..ee09dc1e0b43 100644
--- a/drivers/infiniband/hw/efa/efa_main.c
+++ b/drivers/infiniband/hw/efa/efa_main.c
@@ -17,12 +17,14 @@
#define PCI_DEV_ID_EFA1_VF 0xefa1
#define PCI_DEV_ID_EFA2_VF 0xefa2
#define PCI_DEV_ID_EFA3_VF 0xefa3
+#define PCI_DEV_ID_EFA4_VF 0xefa4
static const struct pci_device_id efa_pci_tbl[] = {
{ PCI_VDEVICE(AMAZON, PCI_DEV_ID_EFA0_VF) },
{ PCI_VDEVICE(AMAZON, PCI_DEV_ID_EFA1_VF) },
{ PCI_VDEVICE(AMAZON, PCI_DEV_ID_EFA2_VF) },
{ PCI_VDEVICE(AMAZON, PCI_DEV_ID_EFA3_VF) },
+ { PCI_VDEVICE(AMAZON, PCI_DEV_ID_EFA4_VF) },
{ }
};
--
2.47.3
next prev parent reply other threads:[~2026-07-12 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 13:44 [PATCH for-next 0/2] RDMA/efa: Add support for 0xefa4 devices Michael Margolin
2026-07-12 13:44 ` [PATCH for-next 1/2] RDMA/efa: Extend page-shift field in MR registration Michael Margolin
2026-07-13 9:31 ` Leon Romanovsky
2026-07-13 12:18 ` Michael Margolin
2026-07-12 13:44 ` Michael Margolin [this message]
2026-07-14 6:51 ` [PATCH for-next 0/2] RDMA/efa: Add support for 0xefa4 devices Leon Romanovsky
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=20260712134413.19226-3-mrgolin@amazon.com \
--to=mrgolin@amazon.com \
--cc=anasmous@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=sleybo@amazon.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.