linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "jaegeuk@kernel.org" <jaegeuk@kernel.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 0/4] fsck: Check write pointers of zoned block devices
Date: Wed, 21 Aug 2019 04:15:46 +0000	[thread overview]
Message-ID: <e13703fcd8d781d4d211651011d16b10f27cdb0d.camel@wdc.com> (raw)
In-Reply-To: <20190820175718.GC58214@jaegeuk-macbookpro.roam.corp.google.com>

On Tue, 2019-08-20 at 10:57 -0700, Jaegeuk Kim wrote:
> Hi Shinichiro,
> 
> Thank you so much for the contribution.
> BTW, I failed to compile them. Could you please take a look at them one more
> time? :)

Thank you for the care and sorry about the compile failure. I checked compile
pass with dev-test branch but did not check with dev branch. I took a look again
and found that I used MAX_BLKADDR() macro added only in the dev-test branch,
which causes the compile failure with dev branch. 

I tried IS_VALID_BLK_ADDR() in place of MAX_BLKADDR() and confirmed it is
working as expected. Will post v2.

--
Best Regards,
Shin'ichiro Kawasaki

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2019-08-21  4:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  8:30 [f2fs-dev] [PATCH 0/4] fsck: Check write pointers of zoned block devices Shin'ichiro Kawasaki
2019-08-19  8:30 ` [f2fs-dev] [PATCH 1/4] libf2fs_zoned: Introduce f2fs_report_zones() helper function Shin'ichiro Kawasaki
2019-08-19  8:30 ` [f2fs-dev] [PATCH 2/4] libf2fs_zoned: Introduce f2fs_reset_zone() function Shin'ichiro Kawasaki
2019-08-19  8:30 ` [f2fs-dev] [PATCH 3/4] fsck.f2fs: Check write pointer consistency with current segments Shin'ichiro Kawasaki
2019-08-19  8:30 ` [f2fs-dev] [PATCH 4/4] fsck.f2fs: Check write pointer consistency with valid blocks count Shin'ichiro Kawasaki
2019-08-20 17:57 ` [f2fs-dev] [PATCH 0/4] fsck: Check write pointers of zoned block devices Jaegeuk Kim
2019-08-21  4:15   ` Shinichiro Kawasaki [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=e13703fcd8d781d4d211651011d16b10f27cdb0d.camel@wdc.com \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).