From: Liu Bo <bo.li.liu@oracle.com>
To: gHcAgree <agree.ms@hotmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: remove unused code in full_send_tree
Date: Tue, 4 Mar 2014 10:17:56 +0800 [thread overview]
Message-ID: <20140304021755.GA27809@localhost.localdomain> (raw)
In-Reply-To: <BLU0-SMTP2745244EE7D59BA5FBAB7A38B8F0@phx.gbl>
On Mon, Mar 03, 2014 at 09:53:45PM +0800, gHcAgree wrote:
>
> On 2014年03月03日 21:31, Liu Bo wrote:
> >It's unnecessary to update key's value, and remove it to keep code clean.
> >
> >Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> >---
> > fs/btrfs/send.c | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> >diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c
> >index 3fe4d6e..a5f9626 100644
> >--- a/fs/btrfs/send.c
> >+++ b/fs/btrfs/send.c
> >@@ -5180,10 +5180,6 @@ static int full_send_tree(struct send_ctx *sctx)
> > if (ret < 0)
> > goto out;
> >- key.objectid = found_key.objectid;
> >- key.type = found_key.type;
> >- key.offset = found_key.offset + 1;
> >-
> > ret = btrfs_next_item(send_root, path);
> > if (ret < 0)
> > goto out;
> Hi Liu and all,
> I think the statements may better be reserved. I noticed that there
> is an "goto join_trans" above. I think we may hit it in the next
> round and exec from the "join_trans" down, then these 3 assignments
> effect.
Yeah, I think you're right, with btrfs-next, we should keep these assignments.
-liubo
prev parent reply other threads:[~2014-03-04 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 13:31 [PATCH 1/2] Btrfs: remove unused code in full_send_tree Liu Bo
2014-03-03 13:31 ` [PATCH 2/2] Btrfs: share the same code for __record_{new,deleted}_ref Liu Bo
2014-03-03 13:53 ` [PATCH 1/2] Btrfs: remove unused code in full_send_tree gHcAgree
2014-03-04 2:17 ` Liu Bo [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=20140304021755.GA27809@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=agree.ms@hotmail.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox