From: Jens Axboe <axboe@kernel.dk>
To: Kent Overstreet <kent.overstreet@gmail.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: Add some exports for bcachefs
Date: Mon, 19 Oct 2020 14:11:44 -0600 [thread overview]
Message-ID: <37a5f032-4979-706b-ea34-926e1756ccb1@kernel.dk> (raw)
In-Reply-To: <20201019190241.2910492-1-kent.overstreet@gmail.com>
On 10/19/20 1:02 PM, Kent Overstreet wrote:
> bcachefs has its own direct IO code.
I talked to Kent about this offline, but just for completeness sake,
my recommendation is to keep these as prep patches for the bcachefs
series so we avoid having modular exports of code that don't have
any in-kernel modular users.
--
Jens Axboe
prev parent reply other threads:[~2020-10-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 19:02 [PATCH 1/2] block: Add some exports for bcachefs Kent Overstreet
2020-10-19 19:02 ` [PATCH 2/2] block: Add blk_status_to_str() Kent Overstreet
2020-10-19 20:11 ` Jens Axboe [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=37a5f032-4979-706b-ea34-926e1756ccb1@kernel.dk \
--to=axboe@kernel.dk \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).