From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [ammarfaizi2-block:rostedt/linux-trace/ftrace/core 30/30] include/linux/cpumask.h:95:42: warning: function 'trace_event_get_offsets_foo_bar' might be a candidate for 'gnu_printf' format attribute
Date: Tue, 19 Jul 2022 08:38:27 +0800 [thread overview]
Message-ID: <a7692c5a-c432-8c51-413d-71072ab2153a@intel.com> (raw)
In-Reply-To: <20220715230441.64c89d63@gandalf.local.home>
On 7/16/2022 11:04 AM, Steven Rostedt wrote:
> On Sat, 16 Jul 2022 09:09:15 +0800
> kernel test robot <lkp@intel.com> wrote:
>
>> All warnings (new ones prefixed by >>):
>>
>> In file included from include/trace/define_trace.h:102,
>> from samples/trace_events/trace-events-sample.h:608,
>> from samples/trace_events/trace-events-sample.c:12:
>> samples/trace_events/./trace-events-sample.h: In function 'trace_event_get_offsets_foo_bar':
>>>> include/linux/cpumask.h:95:42: warning: function 'trace_event_get_offsets_foo_bar' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
>> 95 | #define cpu_possible_mask ((const struct cpumask *)&__cpu_possible_mask)
>> | ^~~~~~~
>
> Please quiet the gnu_printf warning. I actually missed a real build issue
> from the kernel test robot in the last patch set because it was the needle
> in the gnu_printf haystack :-p
>
> That is, after having 10 of these warnings, I missed the one that actually
> mattered.
>
> -- Steve
Hi Steve,
Sorry for the noise, we didn't ignore gnu_printf warning in this file,
we will ignore all gnu_printf warnings.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-07-19 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 1:09 kernel test robot
2022-07-16 3:04 ` Steven Rostedt
2022-07-19 0:38 ` Chen, Rong A [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=a7692c5a-c432-8c51-413d-71072ab2153a@intel.com \
--to=rong.a.chen@intel.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rostedt@goodmis.org \
/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®