All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Johannes Thumshirn <jth@kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: fs/zonefs/./trace.h:22:1: sparse: sparse: cast to restricted blk_opf_t
Date: Wed, 10 Aug 2022 15:21:55 -0700	[thread overview]
Message-ID: <91cdca66-3fd5-667c-de78-113e8a28bb59@acm.org> (raw)
In-Reply-To: <27eed02c-fd92-6f99-b213-1be70193b37d@opensource.wdc.com>

On 8/10/22 12:14, Damien Le Moal wrote:
> Good point. I was using Fedora 36 sparse package. Using sparse compiled from
> source, I now see again the warnings without the patch and no warnings with the
> patch applied. So the patch looks good. Are you going to send it as a fix for
> 6.0-rc1 ?

Hi Damien,

It is not clear to me why I have not yet received any feedback from 
Steven Rostedt on that patch. I will try to ping Steven off-list. If 
necessary I will repost that patch.

Best regards,

Bart.

      reply	other threads:[~2022-08-10 22:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06  8:00 fs/zonefs/./trace.h:22:1: sparse: sparse: cast to restricted blk_opf_t kernel test robot
2022-08-08 14:48 ` Damien Le Moal
2022-08-08 15:37   ` Bart Van Assche
2022-08-10 14:36     ` Damien Le Moal
2022-08-10 18:08       ` Bart Van Assche
2022-08-10 19:14         ` Damien Le Moal
2022-08-10 22:21           ` 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=91cdca66-3fd5-667c-de78-113e8a28bb59@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=jth@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.