From: Bjorn Helgaas <helgaas@kernel.org>
To: Yibo Dong <dong100@mucse.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Add MUCSE vendor ID to pci_ids.h
Date: Wed, 26 Mar 2025 11:57:28 -0500 [thread overview]
Message-ID: <20250326165728.GA1339144@bhelgaas> (raw)
In-Reply-To: <20250325065718.333301-1-dong100@mucse.com>
On Tue, Mar 25, 2025 at 02:57:18PM +0800, Yibo Dong wrote:
> Add MUCSE as a vendor ID (0x8848) for PCI devices so we can use
> the macro for future drivers.
>
> Signed-off-by: Yibo Dong <dong100@mucse.com>
Please post this in the series where you add the future drivers.
We don't add new things to pci_ids.h unless they are actually used by
more than one driver because it complicates life for people who
backport things (there's a note at the top of the file about this).
> ---
> include/linux/pci_ids.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index de5deb1a0118..f1b4c61c6d3c 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -3143,6 +3143,8 @@
> #define PCI_VENDOR_ID_SCALEMP 0x8686
> #define PCI_DEVICE_ID_SCALEMP_VSMP_CTL 0x1010
>
> +#define PCI_VENDOR_ID_MUCSE 0x8848
https://pcisig.com/membership/member-companies?combine=8848 says this
Vendor ID belongs to:
Wuxi Micro Innovation Integrated Circuit Design Co.,Ltd
I suppose "MUCSE" connects with that somehow.
It's nice if people can connect PCI_VENDOR_ID_MUCSE with a name used
in marketing the product. Maybe "MUCSE" is the name under which
Wuxi Micro Innovation Integrated Circuit Design Co.,Ltd markets
products?
> #define PCI_VENDOR_ID_COMPUTONE 0x8e0e
> #define PCI_DEVICE_ID_COMPUTONE_PG 0x0302
> #define PCI_SUBVENDOR_ID_COMPUTONE 0x8e0e
> --
> 2.25.1
>
next prev parent reply other threads:[~2025-03-26 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 6:57 [PATCH] PCI: Add MUCSE vendor ID to pci_ids.h Yibo Dong
2025-03-26 16:57 ` Bjorn Helgaas [this message]
2025-03-27 11:24 ` Yibo Dong
2025-03-27 13:37 ` Bjorn Helgaas
2025-03-28 1:46 ` Yibo Dong
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=20250326165728.GA1339144@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dong100@mucse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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