public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Zhou Shengqing <zhoushengqing@ttyinfo.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Revise some PCI _DSM method implement
Date: Wed, 7 Jan 2026 15:47:11 -0600	[thread overview]
Message-ID: <fb7bdfeb-46a8-444a-b556-77266da3ff3c@kernel.org> (raw)
In-Reply-To: <20250605065814.41298-1-zhoushengqing@ttyinfo.com>

On 6/5/25 1:58 AM, Zhou Shengqing wrote:
> [1/2]PCI/ACPI: Add rev 2 check for PRESERVE_BOOT_CONFIG function
> [2/2]PCI/ACPI: Add acpi_check_dsm() for PCI _DSM definitions
> 
>   drivers/pci/pci-acpi.c | 58 ++++++++++++++++++++++++++++++++----------
>   1 file changed, 44 insertions(+), 14 deletions(-)

Did this series get overlooked?  I was talking to someone about this 
_DSM and noticed it on lore.  It looks reasonable to me.

The only thing that jumped out to me that I would say is that the tag

Fixes: 9d7d5db8e78e ("PCI: Move PRESERVE_BOOT_CONFIG _DSM evaluation to 
pci_re")

Shouldn't be below the cutlist, it should be above it.  If there are no 
other concerns maybe Bjorn can just fix that while committing though.

Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>


      parent reply	other threads:[~2026-01-07 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  6:58 [PATCH v6 0/2] Revise some PCI _DSM method implement Zhou Shengqing
2025-06-05  6:58 ` [PATCH v6 1/2] PCI/ACPI: Add rev 2 check for PRESERVE_BOOT_CONFIG function Zhou Shengqing
2025-06-05  6:58 ` [PATCH v6 2/2] PCI/ACPI: Add acpi_check_dsm() for PCI _DSM definitions Zhou Shengqing
2026-01-07 21:47 ` Mario Limonciello [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=fb7bdfeb-46a8-444a-b556-77266da3ff3c@kernel.org \
    --to=superm1@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=zhoushengqing@ttyinfo.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