public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuai Xue <xueshuai@linux.alibaba.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: lenb@kernel.org, robert.moore@intel.com, andrew@kernel.org,
	bfaccini@nvidia.com, eahariha@linux.microsoft.com,
	dan.j.williams@intel.com, thorsten.blum@linux.dev,
	gourry@gourry.net, nunodasneves@linux.microsoft.com,
	wangyuquan1236@phytium.com.cn, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: [PATCH v2] acpi,srat: Fix incorrect device handle check for Generic Initiator
Date: Tue, 21 Oct 2025 14:54:52 +0800	[thread overview]
Message-ID: <45d5e6a9-d561-4df9-96d4-285f2ca12888@linux.alibaba.com> (raw)
In-Reply-To: <20250915093549.00006109@huawei.com>



在 2025/9/15 16:35, Jonathan Cameron 写道:
> On Sat, 13 Sep 2025 10:32:24 +0800
> Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> 
>> The Generic Initiator Affinity Structure in SRAT table uses device
>> handle type field to indicate the device type. According to ACPI
>> specification, the device handle type value of 1 represents PCI device,
>> not 0.
>>
>> Fixes: 894c26a1c274 ("ACPI: Support Generic Initiator only domains")
>> Reported-by: Wu Zongyong <wuzongyong@linux.alibaba.com>
>> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
> 
> Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> 
> Thanks!
> 
>> ---
>> changes since v1: drop changes in actbl3.h to make it easy to progress per Jonathan
>> ---


Hi, Rafael,

Gentle ping.

Are you happy to pick this bugfix up in this cycle?

Thanks.
Shuai

  reply	other threads:[~2025-10-21  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13  2:32 [PATCH v2] acpi,srat: Fix incorrect device handle check for Generic Initiator Shuai Xue
2025-09-15  8:35 ` Jonathan Cameron
2025-10-21  6:54   ` Shuai Xue [this message]
2025-10-21 13:30     ` Rafael J. Wysocki
2025-10-21 15:06       ` Dave Jiang
2025-10-22  2:08         ` Shuai Xue

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=45d5e6a9-d561-4df9-96d4-285f2ca12888@linux.alibaba.com \
    --to=xueshuai@linux.alibaba.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=andrew@kernel.org \
    --cc=bfaccini@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=eahariha@linux.microsoft.com \
    --cc=gourry@gourry.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nunodasneves@linux.microsoft.com \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=thorsten.blum@linux.dev \
    --cc=wangyuquan1236@phytium.com.cn \
    /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