From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Cleanup of bio_get/set
Date: Tue, 2 Jan 2018 16:40:35 +0100 [thread overview]
Message-ID: <20180102154035.GS3553@twin.jikos.cz> (raw)
In-Reply-To: <1513153540-10737-1-git-send-email-nborisov@suse.com>
On Wed, Dec 13, 2017 at 10:25:36AM +0200, Nikolay Borisov wrote:
> Hello,
>
> Here is a series which cleans the btrfs source code of all the redundant
> bio_get/set calls. After it's applied there is only a single bio_get inovcation
> left in __alloc_device for the flush_bio (and that is wrong since it
> leaks the bio, but this will be fixed in a follow up fix).
>
> Nikolay Borisov (4):
> btrfs: Remove redundant bio_get/set calls in compressed read/write
> paths
> btrfs: Remove redundant bio_get/set from submit_dio_repair_bio
> btrfs: Remove redundan bio_get/bio_set pair from submit_one_bio
> btrfs: Remove redundant pair of bio_get/set in __btrfs_submit_dio_bio
All
Reviewed-by: David Sterba <dsterba@suse.com>
and added to 4.16 queue.
prev parent reply other threads:[~2018-01-02 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 8:25 [PATCH 0/4] Cleanup of bio_get/set Nikolay Borisov
2017-12-13 8:25 ` [PATCH 1/4] btrfs: Remove redundant bio_get/set calls in compressed read/write paths Nikolay Borisov
2017-12-13 8:25 ` [PATCH 2/4] btrfs: Remove redundant bio_get/set from submit_dio_repair_bio Nikolay Borisov
2017-12-13 8:25 ` [PATCH 3/4] btrfs: Remove redundan bio_get/bio_set pair from submit_one_bio Nikolay Borisov
2017-12-13 8:25 ` [PATCH 4/4] btrfs: Remove redundant pair of bio_get/set in __btrfs_submit_dio_bio Nikolay Borisov
2018-01-02 15:40 ` David Sterba [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=20180102154035.GS3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).