From: Josef Bacik <josef@toxicpanda.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
Qu Wenruo <wqu@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-btrfs@vger.kernel.org
Subject: Re: move the low-level btrfs_bio code into a separate file (resent)
Date: Mon, 12 Sep 2022 14:02:55 -0400 [thread overview]
Message-ID: <Yx90T39LITBQPrZs@localhost.localdomain> (raw)
In-Reply-To: <20220912141121.3744931-1-hch@lst.de>
On Mon, Sep 12, 2022 at 04:11:19PM +0200, Christoph Hellwig wrote:
> [resending because I forgot to Cc the btrfs list, sorry]
>
> Hi all,
>
> this small series creates a new bio.c file (and a bio.h header for it)
> to contain all the "storage" layer code below btrfs_submit_bio. The
> amount of code sitting below btrfs_submit_bio will grow a lot with
> the "consolidate btrfs checksumming, repair and bio splitting" series,
> so this pure code move series triest to prepare for that by making
> sure we have a neat file to add it to.
You can add
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
to the series, thanks,
Josef
prev parent reply other threads:[~2022-09-12 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 14:11 move the low-level btrfs_bio code into a separate file (resent) Christoph Hellwig
2022-09-12 14:11 ` [PATCH 1/2] btrfs: split the bio submission path into a separate file Christoph Hellwig
2022-09-12 15:27 ` Johannes Thumshirn
2022-09-13 5:08 ` Christoph Hellwig
2022-09-21 9:40 ` David Sterba
2022-09-22 6:39 ` Christoph Hellwig
2022-09-12 14:11 ` [PATCH 2/2] btrfs: move repair_io_failure to bio.c Christoph Hellwig
2022-09-12 15:28 ` Johannes Thumshirn
2022-09-12 18:02 ` Josef Bacik [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=Yx90T39LITBQPrZs@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.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 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.