From: Pengpeng Hou <hppiscas@163.com>
To: linosanfilippo@gmx.de
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org,
richardcochran@gmail.com, hppiscas@163.com
Subject: [PATCH net v2] net: alacritech: publish the PCI module aliases
Date: Sun, 20 Sep 2026 11:46:51 +0800 [thread overview]
Message-ID: <20260920034651.18109-1-hppiscas@163.com> (raw)
The SLIC driver has a PCI ID table connected to its pci_driver, but does
not export it. Its module therefore lacks the PCI aliases used to
automatically load it for the supported Alacritech adapters.
Export the existing PCI table without changing device matching.
The issue was found by our static-analysis tool.
Fixes: 60c140df15db ("net: ethernet: slicoss: add slicoss gigabit ethernet driver")
Reviewed-by: Simon Horman <horms@kernel.org>
Reviewed-by: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Assisted-by: gpt 5
Signed-off-by: Pengpeng Hou <hppiscas@163.com>
---
Changes since v1:
https://lore.kernel.org/all/20260704152053.49780-1-pengpeng@iscas.ac.cn/
Rewrite the source-analysis explanation as requested by Jakub; retain
the one-line change reviewed by Simon and Lino.
drivers/net/ethernet/alacritech/slicoss.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/alacritech/slicoss.c b/drivers/net/ethernet/alacritech/slicoss.c
index c1949ca060ca..14b74c09233e 100644
--- a/drivers/net/ethernet/alacritech/slicoss.c
+++ b/drivers/net/ethernet/alacritech/slicoss.c
@@ -34,6 +34,7 @@ static const struct pci_device_id slic_id_tbl[] = {
PCI_DEVICE_ID_ALACRITECH_OASIS) },
{ 0 }
};
+MODULE_DEVICE_TABLE(pci, slic_id_tbl);
static const char slic_stats_strings[][ETH_GSTRING_LEN] = {
"rx_packets",
base-commit: 518e5b794c06c0f0eb40df3e202274a66202c137
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-09-20 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 3:46 Pengpeng Hou [this message]
2026-09-22 0:30 ` 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=20260920034651.18109-1-hppiscas@163.com \
--to=hppiscas@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linosanfilippo@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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
all inboxes | Powered by JetHome®