From: Josef Bacik <josef@toxicpanda.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Open code insert_extent_backref
Date: Wed, 4 Mar 2020 13:49:58 -0500 [thread overview]
Message-ID: <3ee8178f-b43a-6267-09f2-5538bb9f7aa6@toxicpanda.com> (raw)
In-Reply-To: <20200304093353.26248-1-nborisov@suse.com>
On 3/4/20 4:33 AM, Nikolay Borisov wrote:
> No need to add a level of indirection for hiding a simple 'if'. Open
> code insert_extent_backref in its sole caller. No functional changes.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2020-03-04 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 9:33 [PATCH] btrfs: Open code insert_extent_backref Nikolay Borisov
2020-03-04 18:49 ` Josef Bacik [this message]
2020-03-04 19:27 ` 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=3ee8178f-b43a-6267-09f2-5538bb9f7aa6@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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
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