Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil V L <sunilvl@ventanamicro.com>
To: Haibo Xu <haibo1.xu@intel.com>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: arnd@arndb.de, xiaobo55x@gmail.com, ajones@ventanamicro.com,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"WANG Xuerui" <kernel@xen0n.name>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Len Brown" <lenb@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Charlie Jenkins" <charlie@rivosinc.com>,
	"Baoquan He" <bhe@redhat.com>, "Evan Green" <evan@rivosinc.com>,
	"Clément Léger" <cleger@rivosinc.com>,
	"Zong Li" <zong.li@sifive.com>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Samuel Holland" <samuel.holland@sifive.com>,
	"Chen Jiahao" <chenjiahao16@huawei.com>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	"Jisheng Zhang" <jszhang@kernel.org>,
	"James Morse" <james.morse@arm.com>,
	"Andy Chiu" <andy.chiu@sifive.com>,
	"Marc Zyngier" <maz@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Tony Luck" <tony.luck@intel.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Alison Schofield" <alison.schofield@intel.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Robert Richter" <rrichter@amd.com>,
	"Yuntao Wang" <ytcoode@gmail.com>,
	"Dave Jiang" <dave.jiang@intel.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	linux-riscv@lists.infradead.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Add ACPI NUMA support for RISC-V
Date: Mon, 1 Jul 2024 11:22:03 +0530	[thread overview]
Message-ID: <ZoJEA85utEK6u36t@sunil-laptop> (raw)
In-Reply-To: <cover.1718268003.git.haibo1.xu@intel.com>

On Thu, Jun 13, 2024 at 04:54:32PM +0800, Haibo Xu wrote:
> This patch series enable RISC-V ACPI NUMA support which was based on
> the recently approved ACPI ECR[1].
> 
> Patch 1/4 add RISC-V specific acpi_numa.c file to parse NUMA information
> from SRAT and SLIT ACPI tables.
> Patch 2/4 add the common SRAT RINTC affinity structure handler.
> Patch 3/4 change the ACPI_NUMA to a hidden option since it would be selected
> by default on all supported platform.
> Patch 4/4 replace pr_info with pr_debug in arch_acpi_numa_init() to avoid
> potential boot noise on ACPI platforms that are not NUMA.
> 
> Based-on: https://github.com/linux-riscv/linux-riscv/tree/for-next
> 
> [1] https://drive.google.com/file/d/1YTdDx2IPm5IeZjAW932EYU-tUtgS08tX/view?usp=sharing

Hi Palmer,

Can this series be taken for -next?

Thanks,
Sunil


  parent reply	other threads:[~2024-07-01  5:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  8:54 [PATCH v4 0/4] Add ACPI NUMA support for RISC-V Haibo Xu
2024-06-13  8:54 ` [PATCH v4 1/4] ACPI: RISCV: Add NUMA support based on SRAT and SLIT Haibo Xu
2024-07-23 13:29   ` Andrew Jones
2024-07-23 14:21     ` Haibo Xu
2024-07-23 14:50       ` Anup Patel
2024-07-23 14:53         ` Haibo Xu
2024-06-13  8:54 ` [PATCH v4 2/4] ACPI: NUMA: Add handler for SRAT RINTC affinity structure Haibo Xu
2024-06-13  8:54 ` [PATCH v4 3/4] ACPI: NUMA: change the ACPI_NUMA to a hidden option Haibo Xu
2024-06-17 13:34   ` Haibo Xu
2024-06-18 15:18     ` Will Deacon
2024-06-19  1:17       ` Haibo Xu
2024-06-19  2:24         ` Huacai Chen
2024-06-13  8:54 ` [PATCH v4 4/4] ACPI: NUMA: replace pr_info with pr_debug in arch_acpi_numa_init Haibo Xu
2024-06-24  2:26 ` [PATCH v4 0/4] Add ACPI NUMA support for RISC-V Hanjun Guo
2024-07-01  5:52 ` Sunil V L [this message]
2024-07-23 12:58 ` patchwork-bot+linux-riscv
2024-07-24 14:50 ` Palmer Dabbelt
2024-07-24 14:56   ` Haibo Xu

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=ZoJEA85utEK6u36t@sunil-laptop \
    --to=sunilvl@ventanamicro.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ajones@ventanamicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexghiti@rivosinc.com \
    --cc=alison.schofield@intel.com \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=charlie@rivosinc.com \
    --cc=chenhuacai@kernel.org \
    --cc=chenjiahao16@huawei.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=evan@rivosinc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haibo1.xu@intel.com \
    --cc=james.morse@arm.com \
    --cc=jszhang@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rafael@kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rrichter@amd.com \
    --cc=samitolvanen@google.com \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=will@kernel.org \
    --cc=xiaobo55x@gmail.com \
    --cc=ytcoode@gmail.com \
    --cc=zong.li@sifive.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