From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gang Li <ligang.bdlg@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Jan 29 (fs/Kconfig: HUGETLBFS)
Date: Mon, 29 Jan 2024 19:50:37 -0800 [thread overview]
Message-ID: <ec5dc528-2c3c-4444-9e88-d2c48395b433@infradead.org> (raw)
In-Reply-To: <20240129143030.16647483@canb.auug.org.au>
On 1/28/24 19:30, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20240125:
>
> New trees: i2c-host-fixes, i2c-host
>
This
menuconfig HUGETLBFS
bool "HugeTLB file system support"
depends on X86 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS || BROKEN
depends on (SYSFS || SYSCTL)
select MEMFD_CREATE
select PADATA
doesn't play nicely when CONFIG_SMP is not set, since PADATA depends on SMP.
This warning occurs on multiple arches:
WARNING: unmet direct dependencies detected for PADATA
Depends on [n]: SMP [=n]
Selected by [y]:
- HUGETLBFS [=y] && (X86 [=y] || SPARC64 || ARCH_SUPPORTS_HUGETLBFS [=n] || BROKEN [=n]) && (SYSFS [=y] || SYSCTL [=n])
--
#Randy
next prev parent reply other threads:[~2024-01-30 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 3:30 linux-next: Tree for Jan 29 Stephen Rothwell
2024-01-30 3:50 ` Randy Dunlap [this message]
2024-01-30 3:55 ` linux-next: Tree for Jan 29 (drm/xe/ and FB_IOMEM_HELPERS) Randy Dunlap
2024-01-30 4:06 ` linux-next: Tree for Jan 29 (soc/tegra/fuse/fuse-tegra30.c) Randy Dunlap
2024-01-30 10:46 ` Jon Hunter
2024-01-30 10:59 ` Arnd Bergmann
2024-01-30 11:02 ` Jon Hunter
2024-02-01 15:07 ` Thierry Reding
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=ec5dc528-2c3c-4444-9e88-d2c48395b433@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ligang.bdlg@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).