From: Bart Van Assche <bvanassche@acm.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
Date: Thu, 6 Oct 2022 10:07:42 -0700 [thread overview]
Message-ID: <712a9412-795a-29ae-002e-4a77356ddffe@acm.org> (raw)
In-Reply-To: <202210062152.UVjgI2io-lkp@intel.com>
On 10/6/22 06:49, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
> fs/jbd2/journal.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/jbd2.h):
>>> include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/jbd2.h:356:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/jbd2.h:356:1: sparse: sparse: restricted blk_opf_t degrades to integer
>>> include/trace/events/jbd2.h:356:1: sparse: sparse: restricted blk_opf_t degrades to integer
I cannot reproduce this. The above warnings should have been fixed by commit
92d23c6e9415 ("overflow, tracing: Define the is_signed_type() macro once").
Bart.
next prev parent reply other threads:[~2022-10-06 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:49 kernel test robot
2022-10-06 17:07 ` Bart Van Assche [this message]
2024-01-09 3:23 kernel test robot
2024-01-15 4:28 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=712a9412-795a-29ae-002e-4a77356ddffe@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=kbuild-all@lists.01.org \
--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®