mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: "rom.wang" <r4o5m6e8o@163.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 Conor Dooley <conor.dooley@microchip.com>,
	 Ryan Roberts <ryan.roberts@arm.com>,
	Sean Chang <seanwascoding@gmail.com>,
	 Anshuman Khandual <anshuman.khandual@arm.com>,
	 Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Yufeng Wang <wangyufeng@kylinos.cn>
Subject: Re: [PATCH] riscv: acpi: update FADT revision check to 6.6
Date: Mon, 23 Mar 2026 17:42:16 -0600 (MDT)	[thread overview]
Message-ID: <3de0f696-0710-fe99-9052-5dc643936aca@kernel.org> (raw)
In-Reply-To: <20260305091433.83983-1-r4o5m6e8o@163.com>

On Thu, 5 Mar 2026, rom.wang wrote:

> From: Yufeng Wang <wangyufeng@kylinos.cn>
> 
> ACPI 6.6 is required for RISC-V as it introduces RISC-V specific
> tables such as RHCT (RISC-V Hart Capabilities Table) and
> RIMT (RISC-V I/O Mapping Table).
> 
> Update the FADT revision check from 6.5 to 6.6 and remove
> the TODO comment since ACPI 6.6 has been officially released.
> 
> Signed-off-by: Yufeng Wang <wangyufeng@kylinos.cn>

Thanks, queued for v7.1.


- Paul

      parent reply	other threads:[~2026-03-23 23:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  9:14 rom.wang
2026-03-05 13:00 ` Heinrich Schuchardt
2026-03-05 14:19   ` Yao Zi
2026-03-11  8:45 ` Sunil V L
2026-03-23 23:42 ` Paul Walmsley [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=3de0f696-0710-fe99-9052-5dc643936aca@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=anshuman.khandual@arm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=r4o5m6e8o@163.com \
    --cc=ryan.roberts@arm.com \
    --cc=seanwascoding@gmail.com \
    --cc=wangyufeng@kylinos.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
Powered by JetHome