From: Libo Chen <libo.chen@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Steven Rostedt <rostedt@goodmis•org>,
Andrew Morton <akpm@linux-foundation•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: runtime warning after merge of the mm-unstable tree
Date: Wed, 23 Apr 2025 17:04:08 -0700 [thread overview]
Message-ID: <5c93dcbd-2394-41bc-923d-5902f4d5aa9a@oracle.com> (raw)
In-Reply-To: <20250423102903.37f9d07c@gandalf.local.home>
On 4/23/25 07:29, Steven Rostedt wrote:
> On Tue, 22 Apr 2025 19:28:16 -0400
> Steven Rostedt <rostedt@goodmis•org> wrote:
>
>> On Wed, 23 Apr 2025 09:16:56 +1000
>> Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>>> On Tue, 22 Apr 2025 11:05:10 -0700 Libo Chen <libo.chen@oracle•com> wrote:
>>>>
>>>> Just to verify, does the build have commit 'tracing: Verify event
>>>> formats that have "%*p.."'[1] or not? I do see linux-next/master has
>>>> it but just want to first confirm that.
>>>
>>> Yes, it does have that commit (since it has been in Linus' tree since
>>> April 4).
>>
>> Looks like we need to teach the verifier about nodemask_pr_args() :-/
>>
>
> No, actually, the verifier found a bug!
>
v4 is sent, should fix this bug~
- Libo
next prev parent reply other threads:[~2025-04-24 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 10:57 linux-next: runtime warning after merge of the mm-unstable tree Stephen Rothwell
2025-04-22 18:05 ` Libo Chen
2025-04-22 23:16 ` Stephen Rothwell
2025-04-22 23:28 ` Steven Rostedt
2025-04-23 6:12 ` Venkat Rao Bagalkote
2025-04-23 14:29 ` Steven Rostedt
2025-04-24 0:04 ` Libo Chen [this message]
2025-04-23 5:19 ` Aithal, Srikanth
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=5c93dcbd-2394-41bc-923d-5902f4d5aa9a@oracle.com \
--to=libo.chen@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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