From: patchwork-bot+linux-riscv@kernel.org
To: Xu@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Haibo1 <haibo1.xu@intel.com>
Cc: linux-riscv@lists.infradead.org, sunilvl@ventanamicro.com,
xiaobo55x@gmail.com, ajones@ventanamicro.com,
catalin.marinas@arm.com, will@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, Jonathan.Cameron@huawei.com,
gshan@redhat.com, rmk+kernel@armlinux.org.uk,
james.morse@arm.com, guohanjun@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: NUMA: initialize all values of acpi_early_node_map to NUMA_NO_NODE
Date: Tue, 24 Sep 2024 06:40:30 +0000 [thread overview]
Message-ID: <172716003024.3899939.517065140587976451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240729035958.1957185-1-haibo1.xu@intel.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 29 Jul 2024 11:59:55 +0800 you 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.
>
> Suggested-by: Andrew Jones <ajones@ventanamicro.com>
> Signed-off-by: Haibo Xu <haibo1.xu@intel.com>
>
> [...]
Here is the summary with links:
- ACPI: NUMA: initialize all values of acpi_early_node_map to NUMA_NO_NODE
https://git.kernel.org/riscv/c/732b177663e1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-09-24 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 3:59 [PATCH] ACPI: NUMA: initialize all values of acpi_early_node_map to NUMA_NO_NODE 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
2024-09-24 6:40 ` patchwork-bot+linux-riscv [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=172716003024.3899939.517065140587976451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Xu@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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=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=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).