From: Keith Busch <keith.busch@intel.com>
To: Helen Koike <helen.koike@collabora.com>
Cc: Christoph Hellwig <hch@infradead.org>,
fes@google.com, axboe@fb.com, rlnelson@google.com,
"open list : NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
mikew@google.com, digitaleric@google.com, monish@google.com,
"james_p_freyensee @ linux . intel . com"
<james_p_freyensee@linux.intel.com>,
tytso@mit.edu, mlin@kernel.org, sagi@grimberg.me,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] nvme: improve performance for virtual NVMe devices
Date: Mon, 17 Apr 2017 19:01:40 -0400 [thread overview]
Message-ID: <20170417230140.GA16224@localhost.localdomain> (raw)
In-Reply-To: <9a406abf-1f39-003d-2863-144c4a263604@collabora.com>
On Fri, Apr 14, 2017 at 03:10:30PM -0300, Helen Koike wrote:
> + Add missing maintainers from scripts/get_maintainer.pl in the email thread
>
> Hi,
>
> I would like to know if it would be possible to get this patch for kernel
> 4.12.
> Should I send a pull request? Or do you usually get the patch from the email
> thread?
Hi Helen,
This looks good to me. I pulled this into a branch for the next merge
window here:
http://git.infradead.org/nvme.git/shortlog/refs/heads/for-next
There's only one other commit at the moment in addition to yours, so
I'll just need to make sure we've got everything we want for 4.12 before
submitting our next pull request.
next prev parent reply other threads:[~2017-04-17 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170331070128.GA28852@infradead.org>
[not found] ` <1491839467-11008-1-git-send-email-helen.koike@collabora.com>
2017-04-14 18:10 ` [PATCH v8] nvme: improve performance for virtual NVMe devices Helen Koike
2017-04-17 23:01 ` Keith Busch [this message]
2017-04-17 23:20 ` Helen Koike
2017-04-20 10:22 ` Sagi Grimberg
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=20170417230140.GA16224@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=digitaleric@google.com \
--cc=fes@google.com \
--cc=hch@infradead.org \
--cc=helen.koike@collabora.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mikew@google.com \
--cc=mlin@kernel.org \
--cc=monish@google.com \
--cc=rlnelson@google.com \
--cc=sagi@grimberg.me \
--cc=tytso@mit.edu \
/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