Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A sparse(make C=1) warning in btrfs about the 'blk_opf_t'
Date: Sat, 13 Aug 2022 09:13:24 +0800	[thread overview]
Message-ID: <20220813091324.38BB.409509F4@e16-tech.com> (raw)
In-Reply-To: <60fef86b-2174-e1a9-6d2b-2508fb809f8e@acm.org>

Hi,

> On 8/12/22 17:00, Wang Yugui wrote:
> > Hi, Bart Van Assche
> >
> > A sparse(make C=1) warning in btrfs about the 'blk_opf_t'
> >
> > ./include/trace/events/btrfs.h:2327:1: warning: incorrect type in assignment (different base types)
> > ./include/trace/events/btrfs.h:2327:1:    expected unsigned char [usertype] opf
> > ./include/trace/events/btrfs.h:2327:1:    got restricted blk_opf_t enum req_op
> 
> Hi Wang,
> 
> Please help with verifying whether this patch fixes that warning: "[PATCH] tracing: Suppress sparse warnings triggered by is_signed_type()" (https://lore.kernel.org/all/20220717151047.19220-1-bvanassche@acm.org/).
> 
> Thanks,
> 
> Bart.

This warning is still ON after applied this patch([PATCH] tracing: Suppress sparse warnings triggered by is_signed_type())

Mabye '(different base types)' is a key in this case.

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2022/08/13


  reply	other threads:[~2022-08-13  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13  0:00 A sparse(make C=1) warning in btrfs about the 'blk_opf_t' Wang Yugui
2022-08-13  0:22 ` Bart Van Assche
2022-08-13  1:13   ` Wang Yugui [this message]
2022-08-13  3:02     ` Bart Van Assche
2022-08-13  4:53       ` Wang Yugui
2022-08-13 15:25         ` Bart Van Assche
2022-08-13 16:03           ` Wang Yugui

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=20220813091324.38BB.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=bvanassche@acm.org \
    --cc=linux-btrfs@vger.kernel.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