From: Philip Li <philip.li@intel.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Yuwen Chen <ywen.chen@foxmail.com>,
<oe-kbuild-all@lists.linux.dev>, <akpm@linux-foundation.org>,
<andrealmeid@igalia.com>, <bigeasy@linutronix.de>,
<colin.i.king@gmail.com>, <dave@stgolabs.net>,
<dvhart@infradead.org>, <edliaw@google.com>,
<justinstitt@google.com>, <kernel-team@android.com>,
<licayy@foxmail.com>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <luto@mit.edu>,
<mingo@redhat.com>, <morbo@google.com>, <nathan@kernel.org>,
<nick.desaulniers+lkml@gmail.com>, <peterz@infradead.org>,
<shuah@kernel.org>, <usama.anjum@collabora.com>,
<wakel@google.com>
Subject: Re: [PATCH] selftests/futex: fix incorrect result reporting of futex_wait test item
Date: Sat, 14 Feb 2026 10:25:45 +0800 [thread overview]
Message-ID: <aY/dKeRABv1uI6ZZ@rli9-mobl> (raw)
In-Reply-To: <87fr7581we.ffs@tglx>
On Fri, Feb 13, 2026 at 09:48:33AM +0100, Thomas Gleixner wrote:
> On Thu, Feb 05 2026 at 23:29, kernel test robot wrote:
>
> > compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
>
> >>> futex_wait.c:48:2: warning: format specifies type 'uintmax_t' (aka 'unsigned long') but the argument has type 'uintmax_t' (aka 'unsigned long long') [-Wformat]
>
> Priceless. Your compiler can't make it's mind up.
>
> uintmax_t is defined by the compiler provided includes.
Got it, sorry for the false report, the cross compiling env in 0day is not set
correctly when building the user space kselftest, I will investigate and fix it
in earliest time.
>
> Thanks,
>
> tglx
>
prev parent reply other threads:[~2026-02-14 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 3:05 Yuwen Chen
2026-02-05 22:29 ` kernel test robot
2026-02-13 8:48 ` Thomas Gleixner
2026-02-14 2:25 ` Philip Li [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=aY/dKeRABv1uI6ZZ@rli9-mobl \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=colin.i.king@gmail.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=edliaw@google.com \
--cc=justinstitt@google.com \
--cc=kernel-team@android.com \
--cc=licayy@foxmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@mit.edu \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=wakel@google.com \
--cc=ywen.chen@foxmail.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
all inboxes | Powered by JetHome®