Linux ACPI
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Robin Murphy <robin.murphy@arm.com>,
	guohanjun@huawei.com, sudeep.holla@arm.com,
	lorenzo.pieralisi@arm.com
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
	Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH v2] ACPI/IORT: Check node revision for PMCG resources
Date: Wed,  9 Feb 2022 18:24:05 +0000	[thread overview]
Message-ID: <164443102845.196616.8228457095383066529.b4-ty@arm.com> (raw)
In-Reply-To: <75628ae41c257fb73588f7bf1c4459160e04be2b.1643916258.git.robin.murphy@arm.com>

On Thu, 3 Feb 2022 19:31:24 +0000, Robin Murphy wrote:
> The original version of the IORT PMCG definition had an oversight
> wherein there was no way to describe the second register page for an
> implementation using the recommended RELOC_CTRS feature. Although the
> spec was fixed, and the final patches merged to ACPICA and Linux written
> against the new version, it seems that some old firmware based on the
> original revision has survived and turned up in the wild.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] ACPI/IORT: Check node revision for PMCG resources
      https://git.kernel.org/arm64/c/da5fb9e1ad3f

(also added a cc stable)

-- 
Catalin


      parent reply	other threads:[~2022-02-09 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 19:31 [PATCH v2] ACPI/IORT: Check node revision for PMCG resources Robin Murphy
2022-02-08 11:10 ` Lorenzo Pieralisi
2022-02-09 18:24 ` Catalin Marinas [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=164443102845.196616.8228457095383066529.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mpetlan@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=will@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