From: "hans.zhang" <hans.zhang@cixtech.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: bhelgaas@google.com, cix-kernel-upstream@cixtech.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Chen <peter.chen@cixtech.com>
Subject: Re: [PATCH] PCI: pci_ids: Add Cixtech P1 Platforms vendor and device ID
Date: Thu, 6 Mar 2025 11:24:42 +0800 [thread overview]
Message-ID: <2112b1dc-7ac6-4d4b-a9a1-1b57d414aae4@cixtech.com> (raw)
In-Reply-To: <20250305174931.GA304679@bhelgaas>
On 2025/3/6 01:49, Bjorn Helgaas wrote:
> EXTERNAL EMAIL
>
> On Wed, Mar 05, 2025 at 02:30:18PM +0800, hans.zhang@cixtech.com wrote:
>> From: Hans Zhang <hans.zhang@cixtech.com>
>>
>> Add Cixtech P1 (internal name sky1) as a vendor and device ID for PCI
>> devices so we can use the macro for future drivers.
>
> See note at top of file:
>
> * Please keep sorted by numeric Vendor ID and Device ID.
> *
> * Do not add new entries to this file unless the definitions
> * are shared between multiple drivers.
>
> Include this patch in a series that shows multiple drivers using it
> and mention those drivers in the commit log.
OK. I will submit it together and use it in the future when our PCIe
controller drives upsteam.
>
> Update the subject line to match the existing style (use "git log
> --oneline include/linux/pci_ids.h"):
>
> PCI: Add Cix Technology Vendor and Device ID
Will change.
>
>> Signed-off-by: Hans Zhang <hans.zhang@cixtech.com>
>> Reviewed-by: Peter Chen <peter.chen@cixtech.com>
>> ---
>> include/linux/pci_ids.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
>> index 1a2594a38199..531b34c1181a 100644
>> --- a/include/linux/pci_ids.h
>> +++ b/include/linux/pci_ids.h
>> @@ -200,6 +200,9 @@
>> #define PCI_DEVICE_ID_COMPAQ_THUNDER 0xf130
>> #define PCI_DEVICE_ID_COMPAQ_NETFLEX3B 0xf150
>>
>> +#define PCI_VENDOR_ID_CIX 0x1f6c
>> +#define PCI_DEVICE_ID_CIX_SKY1 0x0001
>
> This is not sorted by Vendor ID.
Will change.
>
>> #define PCI_VENDOR_ID_NCR 0x1000
>> #define PCI_VENDOR_ID_LSI_LOGIC 0x1000
>> #define PCI_DEVICE_ID_NCR_53C810 0x0001
>>
>> base-commit: 99fa936e8e4f117d62f229003c9799686f74cebc
>> --
>> 2.47.1
>>
prev parent reply other threads:[~2025-03-06 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:30 hans.zhang
2025-03-05 17:49 ` Bjorn Helgaas
2025-03-06 3:24 ` hans.zhang [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=2112b1dc-7ac6-4d4b-a9a1-1b57d414aae4@cixtech.com \
--to=hans.zhang@cixtech.com \
--cc=bhelgaas@google.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peter.chen@cixtech.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®