From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: David Hildenbrand <david@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mm-commits@vger.kernel.org
Subject: Re: [akpm-mm:mm-new] BUILD SUCCESS WITH UNVERIFIED WARNING f4b4fac1867633ac17c35842f03933f6a7a4425f
Date: Thu, 2 Jul 2026 10:48:09 -0700 [thread overview]
Message-ID: <20260702104809.6a137d91eb7e42875b16afda@linux-foundation.org> (raw)
In-Reply-To: <202607022346.lOHuTDpa-lkp@intel.com>
On Thu, 02 Jul 2026 23:31:59 +0800 kernel test robot <lkp@intel.com> wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
> branch HEAD: f4b4fac1867633ac17c35842f03933f6a7a4425f mm/swap, PM: hibernate: atomically replace hibernation pin
>
> Unverified Warning (likely false positive, kindly check if interested):
>
> https://lore.kernel.org/oe-kbuild/202607021433.DYT5fDqE-lkp@intel.com
>
> mm/vmpressure.c:254 vmpressure() warn: check likely/unlikely parentheses
>
> Warning ids grouped by kconfigs:
>
> recent_errors
> `-- microblaze-randconfig-r071-20260702
> `-- mm-vmpressure.c-vmpressure()-warn:check-likely-unlikely-parentheses
Thanks.
I can't reproduce this with that .config and microblaze gcc-15.2.0 or
gcc-16.1.0. And I can't see anything wrong with
if (cgroup_subsys_on_dfl(memory_cgrp_subsys) == tree)
return;
prev parent reply other threads:[~2026-07-03 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 15:31 [akpm-mm:mm-new] BUILD SUCCESS WITH UNVERIFIED WARNING f4b4fac1867633ac17c35842f03933f6a7a4425f kernel test robot
2026-07-02 17:48 ` Andrew Morton [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=20260702104809.6a137d91eb7e42875b16afda@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mm-commits@vger.kernel.org \
/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