mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>,
	Ryusuke Konishi <konishi.ryusuke@gmail.com>
Subject: Re: include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
Date: Thu, 4 Aug 2022 20:07:20 -0700	[thread overview]
Message-ID: <18f28bb5-d8ac-20a5-fd6a-932cda454209@acm.org> (raw)
In-Reply-To: <202208051050.mUx9O9G8-lkp@intel.com>

On 8/4/22 19:03, 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
> 
> vim +191 include/trace/events/nilfs2.h

Hi Luc and Linus,

I think the above sparse warnings refer to the following macro:

#define is_signed_type(type)	(((type)(-1)) < (type)1)

Is the current plan still to modify sparse such that it stops 
complaining about the above macro?

See also 
https://lore.kernel.org/linux-sparse/20220626095814.7wtma47w4sph7dha@mail/

Thanks,

Bart.

  reply	other threads:[~2022-08-05  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  2:03 kernel test robot
2022-08-05  3:07 ` Bart Van Assche [this message]
2024-01-09 14:16 kernel test robot

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=18f28bb5-d8ac-20a5-fd6a-932cda454209@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=kbuild-all@lists.01.org \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=torvalds@linux-foundation.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®