From: Catalin Marinas <catalin.marinas@arm.com>
To: Hanjun Guo <guohanjun@huawei.com>, Will Deacon <will@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Liu Wei <liuwei09@cestc.cn>,
Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Li Chen <me@linux.beauty>
Subject: Re: [PATCH v2 0/2] ACPI: Improve SPCR handling and messaging on SPCR-less systems
Date: Tue, 1 Jul 2025 15:28:21 +0100 [thread overview]
Message-ID: <175138008828.1963850.11865219339288044710.b4-ty@arm.com> (raw)
In-Reply-To: <20250620131309.126555-1-me@linux.beauty>
On Fri, 20 Jun 2025 21:13:06 +0800, Li Chen wrote:
> From: Li Chen <chenl311@chinatelecom.cn>
>
> This small series improves the kernel behavior and output when the ACPI SPCR
> table is not present or not supported.
>
> Currently, even on systems that completely lack an SPCR table, the kernel prints:
> "Use ACPI SPCR as default console: Yes"
>
> [...]
Applied to arm64 (for-next/acpi), thanks!
[1/2] ACPI: Return -ENODEV from acpi_parse_spcr() when SPCR support is disabled
https://git.kernel.org/arm64/c/b9f58d3572a8
[2/2] ACPI: Suppress misleading SPCR console message when SPCR table is absent
https://git.kernel.org/arm64/c/bad3fa2fb920
--
Catalin
prev parent reply other threads:[~2025-07-01 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:13 [PATCH v2 0/2] ACPI: Improve SPCR handling and messaging on SPCR-less systems Li Chen
2025-06-20 13:13 ` [PATCH v2 1/2] ACPI: Return -ENODEV from acpi_parse_spcr() when SPCR support is disabled Li Chen
2025-07-01 11:53 ` Catalin Marinas
2025-07-01 13:54 ` Rafael J. Wysocki
2025-06-20 13:13 ` [PATCH v2 2/2] ACPI: Suppress misleading SPCR console message when SPCR table is absent Li Chen
2025-06-28 7:42 ` [PATCH v2 0/2] ACPI: Improve SPCR handling and messaging on SPCR-less systems Hanjun Guo
2025-07-01 14:28 ` 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=175138008828.1963850.11865219339288044710.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwei09@cestc.cn \
--cc=me@linux.beauty \
--cc=rafael@kernel.org \
--cc=ryan.roberts@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