From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Simon Horman <horms@kernel.org>, Jeff Layton <jlayton@kernel.org>,
Anna Schumaker <anna.schumaker@oracle.com>,
Chuck Lever <chuck.lever@oracle.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Arnd Bergmann <arnd@arndb.de>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Randy Dunlap <rdunlap@infradead.org>,
Yury Norov <ynorov@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: remove __printf() attribute on __ftrace_vbprintk()
Date: Tue, 3 Feb 2026 16:58:08 +0200 [thread overview]
Message-ID: <aYINAPJS9zXlUGCw@smile.fi.intel.com> (raw)
In-Reply-To: <202602032036.FQK7gJvV-lkp@intel.com>
On Tue, Feb 03, 2026 at 08:12:57PM +0800, kernel test robot wrote:
> kernel test robot noticed the following build warnings:
Yeah, you need to go for the full stack of these calls and mark the bottom one
with __diag() to avoid these warnings. That's my understanding and what BPF people
required. Chasing this one-by-one would produce unneeded churn.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-03 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:58 [PATCH] tracing: remove __printf() attribute on __ftrace_vbprintk() Arnd Bergmann
2026-02-02 11:37 ` Jeff Layton
2026-02-02 17:57 ` Andy Shevchenko
2026-02-02 17:59 ` Steven Rostedt
2026-02-03 12:12 ` kernel test robot
2026-02-03 14:58 ` Andy Shevchenko [this message]
2026-02-03 15:56 ` Arnd Bergmann
2026-02-03 17:17 ` Andy Shevchenko
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=aYINAPJS9zXlUGCw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@oracle.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=ynorov@nvidia.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 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.