From: Christoph Hellwig <hch@lst.de>
To: linux-btrfs@vger.kernel.org
Cc: Ming Lei <ming.lei@redhat.com>, Omar Sandoval <osandov@fb.com>,
linux-block@vger.kernel.org
Subject: btrfs bio usage cleanups for multi-page bvec enabledment
Date: Wed, 21 Nov 2018 14:59:06 +0100 [thread overview]
Message-ID: <20181121135908.4720-1-hch@lst.de> (raw)
Hi btrfs maintainers,
can you review and ACK these two btrfs patches that clean up some
interactions with the bio code? I'd like to get these in as the
base of Mings multi-page bio_vec work, which currently contain some
not quite as nice workaround in this area.
next reply other threads:[~2018-11-21 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:59 Christoph Hellwig [this message]
2018-11-21 13:59 ` [PATCH 1/2] btrfs: remove various bio_offset arguments Christoph Hellwig
2018-11-21 14:09 ` David Sterba
2018-11-21 13:59 ` [PATCH 2/2] btrfs: look at bi_size for repair decisions Christoph Hellwig
2018-11-21 14:09 ` 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=20181121135908.4720-1-hch@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.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).