From: Will Deacon <will@kernel.org>
To: sunilvl@ventanamicro.com, Haibo Xu <haibo1.xu@intel.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
xiaobo55x@gmail.com, ajones@ventanamicro.com,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Gavin Shan <gshan@redhat.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
James Morse <james.morse@arm.com>,
Hanjun Guo <guohanjun@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] ACPI: NUMA: initialize all values of acpi_early_node_map to NUMA_NO_NODE
Date: Fri, 16 Aug 2024 16:15:57 +0100 [thread overview]
Message-ID: <172380817082.2918676.9519520229609793025.b4-ty@kernel.org> (raw)
In-Reply-To: <20240729035958.1957185-1-haibo1.xu@intel.com>
On Mon, 29 Jul 2024 11:59:55 +0800, Haibo Xu wrote:
> Currently, only acpi_early_node_map[0] was initialized to NUMA_NO_NODE.
> To ensure all the values were properly initialized, switch to initialize
> all of them to NUMA_NO_NODE.
>
>
Applied arm64 hunk to arm64 (for-next/acpi), thanks!
[1/1] ACPI: NUMA: initialize all values of acpi_early_node_map to NUMA_NO_NODE
https://git.kernel.org/arm64/c/8bb0376fe082
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2024-08-16 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 3:59 Haibo Xu
2024-07-29 6:16 ` Anshuman Khandual
2024-07-29 6:28 ` Sunil V L
2024-07-29 13:05 ` Andrew Jones
2024-08-16 15:15 ` Will Deacon [this message]
2024-09-24 6:40 ` patchwork-bot+linux-riscv
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=172380817082.2918676.9519520229609793025.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=guohanjun@huawei.com \
--cc=haibo1.xu@intel.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sunilvl@ventanamicro.com \
--cc=xiaobo55x@gmail.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
all inboxes | Powered by JetHome®