[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYINAPJS9zXlUGCw@smile.fi.intel.com>
Date: Tue, 3 Feb 2026 16:58:08 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: kernel test robot <lkp@...el.com>
Cc: Arnd Bergmann <arnd@...nel.org>, Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Simon Horman <horms@...nel.org>, Jeff Layton <jlayton@...nel.org>,
Anna Schumaker <anna.schumaker@...cle.com>,
Chuck Lever <chuck.lever@...cle.com>, llvm@...ts.linux.dev,
oe-kbuild-all@...ts.linux.dev, Arnd Bergmann <arnd@...db.de>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Randy Dunlap <rdunlap@...radead.org>,
Yury Norov <ynorov@...dia.com>,
Joel Fernandes <joelagnelf@...dia.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: remove __printf() attribute on
__ftrace_vbprintk()
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
Powered by blists - more mailing lists