public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Hellwig <hch@lst.de>,
	Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: minor bio submission cleanups
Date: Sat, 16 Apr 2022 06:44:05 +0800	[thread overview]
Message-ID: <fc163e9a-ff50-ac31-9b41-fea23913f579@gmx.com> (raw)
In-Reply-To: <20220415143328.349010-1-hch@lst.de>



On 2022/4/15 22:33, Christoph Hellwig wrote:
> Hi all,
>
> this series cleans up a few loose ends in the btrfs bio submission path.

Mind to share which commit your code are based on?

After patch 3/5 "btrfs: do not return errors from
btrfs_submit_metadata_bio", I was expecting the same cleanup for
btrfs_submit_data_bio(), but it doesn't.

Thus I guess it already handled by other patches in your branch?

Thanks,
Qu
>
> Diffstat:
>   compression.c |   11 +++++------
>   compression.h |    4 ++--
>   ctree.h       |    5 ++---
>   disk-io.c     |   26 ++++++++++----------------
>   disk-io.h     |    4 ++--
>   extent_io.c   |   39 +++++++++++++++++++++++++++++++++++----
>   extent_io.h   |   18 ++----------------
>   inode.c       |   49 ++++++++++---------------------------------------
>   8 files changed, 68 insertions(+), 88 deletions(-)

  parent reply	other threads:[~2022-04-15 22:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 14:33 minor bio submission cleanups Christoph Hellwig
2022-04-15 14:33 ` [PATCH 1/5] btrfs: move btrfs_readpage to extent_io.c Christoph Hellwig
2022-04-15 14:33 ` [PATCH 2/5] btrfs: remove the unused bio_flags argument to btrfs_submit_metadata_bio Christoph Hellwig
2022-04-15 22:35   ` Qu Wenruo
2022-04-15 14:33 ` [PATCH 3/5] btrfs: do not return errors from btrfs_submit_metadata_bio Christoph Hellwig
2022-04-15 22:40   ` Qu Wenruo
2022-04-15 14:33 ` [PATCH 4/5] btrfs: do not return errors from btrfs_submit_compressed_read Christoph Hellwig
2022-04-15 22:48   ` Qu Wenruo
2022-04-16  4:49     ` Christoph Hellwig
2022-04-16  6:48       ` Qu Wenruo
2022-04-20 20:45       ` David Sterba
2022-04-15 14:33 ` [PATCH 5/5] btrfs: do not return errors from submit_bio_hook_t instances Christoph Hellwig
2022-04-15 22:49   ` Qu Wenruo
2022-04-15 22:44 ` Qu Wenruo [this message]
2022-04-16  4:46   ` minor bio submission cleanups Christoph Hellwig
2022-04-18  7:23 ` Nikolay Borisov
2022-04-20 19:28 ` 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=fc163e9a-ff50-ac31-9b41-fea23913f579@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.com \
    --cc=hch@lst.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@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