Linux-f2fs-devel Archive on lore.kernel.org
 help / color / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Yuehaibing <yuehaibing@huawei.com>
Cc: "jaegeuk@kernel.org" <jaegeuk@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH -next] f2fs: remove set but not used variable 'cs_block'
Date: Thu, 26 Dec 2019 08:24:20 +0000
Message-ID: <20191226082419.ljbhystwkhp2d4gh@shindev.dhcp.fujisawa.hgst.com> (raw)
In-Reply-To: <62ce1981-9061-f798-a65d-9599ceceb4b8@huawei.com>

On Dec 26, 2019 / 14:05, Yuehaibing wrote:
> On 2019/12/26 11:44, Chao Yu wrote:
> > On 2019/12/24 20:43, YueHaibing wrote:
> >> fs/f2fs/segment.c: In function fix_curseg_write_pointer:
> >> fs/f2fs/segment.c:4485:35: warning: variable cs_block set but not used [-Wunused-but-set-variable]
> >>
> >> It is never used since commit 362d8a920384 ("f2fs: Check
> >> write pointer consistency of open zones") , so remove it.
> > 
> > Thanks for the fix!
> > 
> > Do you mind merging this patch to original patch? as it's still
> > pending in dev branch.
> 
> It's ok for me.
>

Thank you for this catch and the fix. Appreciated.

--
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 index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 12:43 YueHaibing
2019-12-26  3:44 ` Chao Yu
2019-12-26  6:05   ` Yuehaibing
2019-12-26  8:24     ` Shinichiro Kawasaki [this message]
2020-01-15  2:33       ` Shinichiro Kawasaki
2020-01-15  9:54         ` Chao Yu
2020-01-16  0:25           ` Shinichiro Kawasaki
2020-01-15 21:44         ` Jaegeuk Kim

Reply instructions:

You may reply publically 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=20191226082419.ljbhystwkhp2d4gh@shindev.dhcp.fujisawa.hgst.com \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuehaibing@huawei.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

Linux-f2fs-devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-f2fs-devel/0 linux-f2fs-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-f2fs-devel linux-f2fs-devel/ https://lore.kernel.org/linux-f2fs-devel \
		linux-f2fs-devel@lists.sourceforge.net
	public-inbox-index linux-f2fs-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/net.sourceforge.lists.linux-f2fs-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git