From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 5.17-rc4
Date: Fri, 11 Feb 2022 18:53:00 +0000 [thread overview]
Message-ID: <YgawjGlDGS4l5pBY@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 297ae1eb23b04c5a46111ab53c8d0f69af43f402:
arm64: cpufeature: List early Cortex-A510 parts as having broken dbm (2022-01-28 16:15:46 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to da5fb9e1ad3fbf632dce735f1bdad257ca528499:
ACPI/IORT: Check node revision for PMCG resources (2022-02-09 18:16:22 +0000)
----------------------------------------------------------------
arm64 fixes:
- Enable Cortex-A510 erratum 2051678 by default as we do with other
errata.
- arm64 IORT: Check the node revision for PMCG resources to cope with
old firmware based on a broken revision of the spec that had no way to
describe the second register page (when an implementation is using the
recommended RELOC_CTRS feature).
----------------------------------------------------------------
Mark Brown (1):
arm64: Enable Cortex-A510 erratum 2051678 by default
Robin Murphy (1):
ACPI/IORT: Check node revision for PMCG resources
arch/arm64/Kconfig | 1 +
drivers/acpi/arm64/iort.c | 14 +++++++++++---
2 files changed, 12 insertions(+), 3 deletions(-)
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-02-11 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 18:53 Catalin Marinas [this message]
2022-02-11 20:05 ` [GIT PULL] arm64 fixes for 5.17-rc4 pr-tracker-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=YgawjGlDGS4l5pBY@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).