All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: kbuild-all@lists.01.org
Subject: Re: [kdave-btrfs-devel:misc-next 140/144] fs/btrfs/scrub.c:75:44: sparse: sparse: dubious one-bit signed bitfield
Date: Mon, 23 Nov 2020 16:51:46 +0100	[thread overview]
Message-ID: <20201123155146.GC8669@suse.cz> (raw)
In-Reply-To: <4539e453-6067-7aea-48f2-78d6e70b9fd0@suse.com>

[-- Attachment #1: Type: text/plain, Size: 765 bytes --]

On Fri, Nov 20, 2020 at 09:22:43AM +0800, Qu Wenruo wrote:
> > a2de733c78fa7af Arne Jansen    2011-03-08  69  	u64			generation;
> > b5d67f64f9bc656 Stefan Behrens 2012-03-27  70  	u64			logical;
> > b5d67f64f9bc656 Stefan Behrens 2012-03-27  71  	u64			physical;
> > ff023aac31198e8 Stefan Behrens 2012-11-06  72  	u64			physical_for_dev_replace;
> > 570193454a5841a Zhao Lei       2015-01-20  73  	atomic_t		refs;
> > ec9799c7e151eb4 Qu Wenruo      2020-11-13  74  	u8			mirror_num;
> > ec9799c7e151eb4 Qu Wenruo      2020-11-13 @75  	int			have_csum:1;
> > ec9799c7e151eb4 Qu Wenruo      2020-11-13  76  	int			io_error:1;
> 
> Do I need to resend the patch (to use unsigned int) or you can modify it
> on your side?

I've fixed in the local branch.

  reply	other threads:[~2020-11-23 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  0:23 [kdave-btrfs-devel:misc-next 140/144] fs/btrfs/scrub.c:75:44: sparse: sparse: dubious one-bit signed bitfield kernel test robot
2020-11-20  1:22 ` Qu Wenruo
2020-11-23 15:51   ` David Sterba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-19 23:59 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=20201123155146.GC8669@suse.cz \
    --to=dsterba@suse.cz \
    --cc=kbuild-all@lists.01.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.