Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lin Wang <wanglin@open-hieco.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
	yazen.ghannam@amd.com, mario.limonciello@amd.com,
	tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, "H. Peter Anvin" <hpa@zytor.com>,
	bhelgaas@google.com, x86@kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] pci_ids: Add Hygon Family 0x18 DF F3/F4 device IDs
Date: Fri, 4 Sep 2026 11:18:53 +0800	[thread overview]
Message-ID: <cbaa7601-3614-4e76-9d4e-c56e022e0917@open-hieco.net> (raw)
In-Reply-To: <20260903221043.GA2261875@bhelgaas>



On 9/4/2026 6:10 AM, Bjorn Helgaas wrote:
>> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F3	0x1463
>> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F4	0x1464
>> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F3B	0x1493
>> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F4B	0x1494
>> +#define PCI_DEVICE_ID_HYGON_18H_M05H_DF_F3	0x14b3
>> +#define PCI_DEVICE_ID_HYGON_18H_M05H_DF_F4	0x14b4
> It looks like these are only needed in one place, so per the note:
> 
>   *      Do not add new entries to this file unless the definitions
>   *      are shared between multiple drivers.
> 
> the #defines should probably be added in the
> arch/x86/kernel/hygon_node.c (or just use the raw hex values).
> 
> This helps reduce conflicts when backporting changes like this.

Hi Bjorn,

Thanks for pointing this out.

These IDs are only used by the Hygon node code in this series. I will
move the definitions to arch/x86/kernel/hygon_node.c. They can be added 
to pci_ids.h later when needed by in-tree users.

Thanks & Br;

Lin


  reply	other threads:[~2026-09-04  3:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  7:16 [PATCH v4 0/5] x86/hygon: Add Family 0x18 DF node enumeration and SMN access Lin Wang
2026-09-01  7:16 ` [PATCH v4 1/5] pci_ids: Add Hygon Family 0x18 DF F3/F4 device IDs Lin Wang
2026-09-01  7:34   ` sashiko-bot
2026-09-03 22:10   ` Bjorn Helgaas
2026-09-04  3:18     ` Lin Wang [this message]
2026-09-01  7:16 ` [PATCH v4 2/5] x86/hygon: Add Family 0x18 DF node enumeration Lin Wang
2026-09-01  7:29   ` sashiko-bot
2026-09-01  7:16 ` [PATCH v4 3/5] x86/hygon: Map CPU NodeIds to DF nodes Lin Wang
2026-09-01  7:32   ` sashiko-bot
2026-09-01  7:16 ` [PATCH v4 4/5] x86/amd_node: Skip SMN setup on Hygon Fam18h models 0x04-0x08 Lin Wang
2026-09-01  7:34   ` sashiko-bot
2026-09-02  2:48   ` Borislav Petkov
2026-09-02  6:22     ` Lin Wang
2026-09-02 15:13       ` Borislav Petkov
2026-09-03  1:49         ` Lin Wang
2026-09-03 17:34           ` Yazen Ghannam
2026-09-04  2:43             ` Lin Wang
2026-09-04  5:36           ` Borislav Petkov
2026-09-04  6:26             ` Lin Wang
2026-09-01  7:17 ` [PATCH v4 5/5] x86/hygon: Add Family 0x18 SMN access Lin Wang
2026-09-01  7:28   ` sashiko-bot

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=cbaa7601-3614-4e76-9d4e-c56e022e0917@open-hieco.net \
    --to=wanglin@open-hieco.net \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@amd.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