From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Guo Ren <guoren@linux.alibaba.com>, Guo Ren <guoren@kernel.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
linux-riscv@lists.infradead.org, Linux-MM <linux-mm@kvack.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
Andrew Jones <ajones@ventanamicro.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: In-flight collision: ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP renaming
Date: Mon, 24 Apr 2023 11:40:25 +0200 [thread overview]
Message-ID: <CAKXUXMyVeg2kQK_edKHtMD3eADrDK_PKhCSVkMrLDdYgTQQ5rg@mail.gmail.com> (raw)
Dear Guo Ren, dear Palmer,
on linux-next, I have noticed that you have submitted and added the
commit a3c7d6b642e4 ("riscv: mm: hugetlb: Enable
ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP"), that adds the select
ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP to the RISCV config. As it
seems, Aneesh Kumar K.V has concurrently renamed this config
throughout the tree with commit 215218dddd25 ("mm/hugetlb_vmemmap:
rename ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP"), but your commit was
not visible to that renaming. When both commits are merged in a common
tree---as happens with linux-next, and will soon happen with Linus'
tree, your commit a3c7d6b642e4 will do nothing (select no existing
config anymore).
It is easy to fix, adjust this one line to the renaming and 'select
ARCH_WANT_OPTIMIZE_VMEMMAP'. For now, I am just reporting to let you
know; probably, it is best to get a quick fix-up patch with -rc2, once
all the changes landed in -rc1.
Best regards,
Lukas
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-04-24 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:40 Lukas Bulwahn [this message]
2023-04-24 12:13 ` In-flight collision: ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP renaming Matthew Wilcox
2023-05-05 6:15 ` Guo Ren
2023-05-08 4:52 ` Lukas Bulwahn
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=CAKXUXMyVeg2kQK_edKHtMD3eADrDK_PKhCSVkMrLDdYgTQQ5rg@mail.gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=songmuchun@bytedance.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).