From: Miaohe Lin <linmiaohe@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for HUGETLBFS when selected by PPC_8xx
Date: Wed, 5 Feb 2025 10:39:20 +0800 [thread overview]
Message-ID: <29cf621d-db67-6c5c-0dc5-ebe79edc6cc6@huawei.com> (raw)
In-Reply-To: <202501240611.LDmD2nkj-lkp@intel.com>
On 2025/1/24 6:24, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: d0d106a2bd21499901299160744e5fe9f4c83ddb
> commit: f8142cf94d4737ea0c3baffb3b9bad8addcb9b6b hugetlb: make hugetlb depends on SYSFS or SYSCTL
> date: 2 years, 4 months ago
> config: powerpc-kismet-CONFIG_HUGETLBFS-CONFIG_PPC_8xx-0-0 (https://download.01.org/0day-ci/archive/20250124/202501240611.LDmD2nkj-lkp@intel.com/config)
> reproduce: (https://download.01.org/0day-ci/archive/20250124/202501240611.LDmD2nkj-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202501240611.LDmD2nkj-lkp@intel.com/
Thanks for report. Sorry for late respond. I was on my Spring Festival vacation.
>
> kismet warnings: (new ones prefixed by >>)
>>> kismet: WARNING: unmet direct dependencies detected for HUGETLBFS when selected by PPC_8xx
> WARNING: unmet direct dependencies detected for HUGETLBFS
> Depends on [n]: (X86 || IA64 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS [=y] || BROKEN [=n]) && (SYSFS [=n] || SYSCTL [=n])
> Selected by [y]:
> - PPC_8xx [=y] && <choice>
I am a bit confused. HUGETLBFS depends on SYSFS or SYSCTL. How can it be selected while SYSFS [=n] || SYSCTL [=n]?
Or am I miss something?
Thanks.
.
next prev parent reply other threads:[~2025-02-05 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:24 kernel test robot
2025-02-05 2:39 ` Miaohe Lin [this message]
2025-02-05 16:35 ` Christophe Leroy
2025-02-06 2:08 ` Miaohe Lin
2025-02-06 6:30 ` Christophe Leroy
2025-02-06 7:12 ` Miaohe Lin
2025-02-06 8:47 ` Christophe Leroy
2025-02-06 11:39 ` Miaohe Lin
-- strict thread matches above, loose matches on Subject: below --
2025-08-22 12:07 kernel test robot
2025-05-13 7:54 kernel test robot
2025-03-01 1:55 kernel test robot
2023-11-19 4:09 kernel test robot
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=29cf621d-db67-6c5c-0dc5-ebe79edc6cc6@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=fazilyildiran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.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