From: "Matias Bjørling" <m@bjorling.me>
To: Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: nvme patches?
Date: Wed, 14 Jan 2015 10:17:23 +0100 [thread overview]
Message-ID: <54B63423.2040802@bjorling.me> (raw)
In-Reply-To: <20150114084221.GB29714@infradead.org>
On 01/14/2015 09:42 AM, Christoph Hellwig wrote:
> There are a lot of nvme patches and block core pathes to support them
> showing up directly in the block tree that I've never seen anywhere.
>
> Is there a mailinglist where this work happens?
Yes, the nvme dissussions are at linux-nvme@lists.infradead.org /
http://lists.infradead.org/pipermail/linux-nvme/
prev parent reply other threads:[~2015-01-14 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 8:42 nvme patches? Christoph Hellwig
2015-01-14 9:17 ` Matias Bjørling [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=54B63423.2040802@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-fsdevel@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).