mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: 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, Jens Axboe <axboe@kernel.dk>,
	Ryusuke Konishi <konishi.ryusuke@gmail.com>
Subject: Re: [ammarfaizi2-block:axboe/linux-block/for-next 91/112] include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
Date: Sun, 17 Jul 2022 07:50:46 -0700	[thread overview]
Message-ID: <4dc9a4eb-403f-951e-16e3-6fae5ed322be@acm.org> (raw)
In-Reply-To: <202207162314.Jz305X9h-lkp@intel.com>

On 7/16/22 08:40, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
>     fs/nilfs2/segment.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/nilfs2.h):
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer

I think the root cause of this and similar reports is in the tracing 
core core. I will post a patch.

Thanks,

Bart.

      reply	other threads:[~2022-07-17 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 15:40 kernel test robot
2022-07-17 14:50 ` Bart Van Assche [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=4dc9a4eb-403f-951e-16e3-6fae5ed322be@acm.org \
    --to=bvanassche@acm.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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 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®