From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
venkat88@linux.ibm.com
Cc: Libo Chen <libo.chen@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
venkat88@linux.ibm.com
Subject: Re: linux-next: runtime warning after merge of the mm-unstable tree
Date: Wed, 23 Apr 2025 11:42:20 +0530 [thread overview]
Message-ID: <4850a1c9-7aff-4686-aefd-3a2c8d3e7539@linux.ibm.com> (raw)
In-Reply-To: <20250422192816.03eaac09@batman.local.home>
On 23/04/25 4:58 am, Steven Rostedt 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:
Observing same boot warnings on IBM Power9 Servers also.
Regards,
Venkat.
>>> 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() :-/
>
> -- Steve
>
next prev parent reply other threads:[~2025-04-23 6:12 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 [this message]
2025-04-23 14:29 ` Steven Rostedt
2025-04-24 0:04 ` Libo Chen
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=4850a1c9-7aff-4686-aefd-3a2c8d3e7539@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=libo.chen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.