From: David Sterba <dsterba@suse.cz>
To: Hao Peng <flyingpenghao@gmail.com>
Cc: "clm@fb.com" <clm@fb.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"dsterba@suse.com" <dsterba@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: remove redundant code
Date: Fri, 7 Oct 2022 18:32:44 +0200 [thread overview]
Message-ID: <20221007163244.GS13389@twin.jikos.cz> (raw)
In-Reply-To: <CAPm50a+6tGRCkB7=QiA+y5EEPm_40N6d-KChPxnT+40Q=5EUQw@mail.gmail.com>
On Fri, Sep 23, 2022 at 10:56:12PM +0800, Hao Peng wrote:
> From: Peng Hao <flyingpeng@tencent.com>
>
> Since leaf is already NULL, and no other branch will go fail_unlock,
> the fail_unlock branch is useless.
The patch does not aply cleanly, git am says it's corrupted on line 10
but I don't see anything obvious.
The change makes sense, I'll change the subject to "btrfs: simplify
cleanup after error in btrfs_create_tree" and add it to misc-next,
thanks.
next prev parent reply other threads:[~2022-10-07 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:56 [PATCH] btrfs: remove redundant code Hao Peng
2022-10-07 16:32 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-18 7:26 flyingpeng(彭浩)
2017-07-12 6:32 [PATCH] btrfs: Remove " Nikolay Borisov
2017-07-12 14:55 ` David Sterba
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=20221007163244.GS13389@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=flyingpenghao@gmail.com \
--cc=josef@toxicpanda.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 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.