From: Chao Yu <chao2.yu@samsung.com>
To: dh.sim@samsung.com
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] Remove an unnecessary line in allocate_data_block.
Date: Mon, 28 Jul 2014 13:35:37 +0800 [thread overview]
Message-ID: <003c01cfaa25$dc91ac80$95b50580$@samsung.com> (raw)
In-Reply-To: <5225212.3741406502181304.JavaMail.weblogic@epv6ml08>
Hi Dongho,
> -----Original Message-----
> From: Dongho Sim [mailto:dh.sim@samsung.com]
> Sent: Monday, July 28, 2014 7:03 AM
> To: jaegeuk@kernel.org; linux-f2fs-devel@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH] Remove an unnecessary line in allocate_data_block.
>
> Hi. There was an unnecessary line in function, allocate_data_block.
> It is already done in
> refresh_sit_entry(sbi, old_blkaddr, *new_blkaddr);
>
> Thanks.
Agreed,
How about removing old_cursegno too as it's no longer used in allocate_data_block?
Thanks,
Yu
>
> Signed-off-by: Dongho Sim <dh.sim@samsung.com>
> ---
> fs/f2fs/segment.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 8a6e57d..a3c7aae 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1001,7 +1001,6 @@ void allocate_data_block(struct f2fs_sb_info *sbi, struct page *page,
> * since SSR needs latest valid block information.
> */
> refresh_sit_entry(sbi, old_blkaddr, *new_blkaddr);
> - locate_dirty_segment(sbi, old_cursegno);
>
> mutex_unlock(&sit_i->sentry_lock);
>
> --
> 1.9.1
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
next prev parent reply other threads:[~2014-07-28 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 23:03 [PATCH] Remove an unnecessary line in allocate_data_block Dongho Sim
2014-07-28 5:35 ` Chao Yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-28 5:51 Dongho Sim
2014-07-28 7:21 Chao Yu
2014-07-28 8:34 Dongho Sim
2014-07-29 13:24 ` Jaegeuk Kim
2014-07-30 0:24 ` Changman Lee
2014-07-30 1:23 ` Jaegeuk Kim
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='003c01cfaa25$dc91ac80$95b50580$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=dh.sim@samsung.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 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.