From: Mike Rapoport <rppt@kernel.org>
To: Yuquan Wang <wangyuquan1236@phytium.com.cn>
Cc: chenhuacai@kernel.org, kernel@xen0n.name,
jiaxun.yang@flygoat.com, akpm@linux-foundation.org,
david@redhat.com, Jonathan.Cameron@huawei.com,
dave.hansen@linux.intel.com, dan.j.williams@intel.com,
alison.schofield@intel.com, chenbaozi@phytium.com.cn,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH 1/1] LoongArch: Introduce the numa_memblks conversion
Date: Sat, 19 Apr 2025 10:51:46 +0300 [thread overview]
Message-ID: <aANWElXU6wi4QJt2@kernel.org> (raw)
In-Reply-To: <20250409070250.3225839-1-wangyuquan1236@phytium.com.cn>
Hi Yuquan,
On Wed, Apr 09, 2025 at 03:02:50PM +0800, Yuquan Wang wrote:
> "mm: introduce numa_memblks"(87482708210f) has moved numa_memblks
> from x86 to the generic code, but loongarch was left out of this
> conversion.
>
> This patch introduces the generic numa_memblks.
>
> Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
> ---
>
> Background
> ----------
> I am managed to land the patch[1] "mm: numa_memblks: introduce numa_add_reserved_memblk"
> but kernel test CI noticed build errors[2] from loongarch64-linux-gcc.
I think you can just add a dummy static inline numa_add_reserved_memblk()
to arch/loongarch/include/asm/numa.h to fix the build. Then moving
loongarch to numa_memblks won't be a stopper for your change.
> Link:
> [1]: https://lore.kernel.org/all/20250409040121.3212489-1-wangyuquan1236@phytium.com.cn/
> [2]: https://lore.kernel.org/all/202503282026.QNaOAK79-lkp@intel.com/
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-04-19 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 7:02 [PATCH 1/1] LoongArch: Introduce the numa_memblks conversion Yuquan Wang
2025-04-09 14:20 ` Huacai Chen
2025-04-10 23:29 ` kernel test robot
2025-04-19 7:51 ` Mike Rapoport [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=aANWElXU6wi4QJt2@kernel.org \
--to=rppt@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=chenbaozi@phytium.com.cn \
--cc=chenhuacai@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=wangyuquan1236@phytium.com.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.