From: m@bjorling.me (Matias Bjørling)
Subject: [PATCH v4] basic conversion to blk-mq
Date: Mon, 02 Jun 2014 12:31:59 +0200 [thread overview]
Message-ID: <538C529F.1080707@bjorling.me> (raw)
In-Reply-To: <20140602094251.GA30612@infradead.org>
On 06/02/2014 11:42 AM, Christoph Hellwig wrote:
> On Thu, May 29, 2014@11:51:24PM +0200, Matias Bj??rling wrote:
>> Hi Matthew and Keith,
>>
>> Thanks for the quick review.
>>
>> The patch has been updated with the feedback from Keith and Jens. It's against
>> Jens' 3.16/core tree. You may use the nvmemq_wip_review branch at:
>>
>> https://github.com/MatiasBjorling/linux-collab nvmemq_wip_review
>
> It seems like this includes more patches than the one you're sending
> out, care to send the full series next time?
>
Yes. The nvmemq_wip_review currently holds the in-progress v5 patch. I
make sure to split it out for the next serie and onward.
WARNING: multiple messages have this Message-ID (diff)
From: "Matias Bjørling" <m@bjorling.me>
To: Christoph Hellwig <hch@infradead.org>
Cc: willy@linux.intel.com, keith.busch@intel.com,
sbradshaw@micron.com, axboe@kernel.dk,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v4] basic conversion to blk-mq
Date: Mon, 02 Jun 2014 12:31:59 +0200 [thread overview]
Message-ID: <538C529F.1080707@bjorling.me> (raw)
In-Reply-To: <20140602094251.GA30612@infradead.org>
On 06/02/2014 11:42 AM, Christoph Hellwig wrote:
> On Thu, May 29, 2014 at 11:51:24PM +0200, Matias Bj??rling wrote:
>> Hi Matthew and Keith,
>>
>> Thanks for the quick review.
>>
>> The patch has been updated with the feedback from Keith and Jens. It's against
>> Jens' 3.16/core tree. You may use the nvmemq_wip_review branch at:
>>
>> https://github.com/MatiasBjorling/linux-collab nvmemq_wip_review
>
> It seems like this includes more patches than the one you're sending
> out, care to send the full series next time?
>
Yes. The nvmemq_wip_review currently holds the in-progress v5 patch. I
make sure to split it out for the next serie and onward.
next prev parent reply other threads:[~2014-06-02 10:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 21:51 [PATCH v4] basic conversion to blk-mq Matias Bjørling
2014-05-29 21:51 ` Matias Bjørling
2014-05-29 21:51 ` [PATCH v4] NVMe: " Matias Bjørling
2014-05-29 21:51 ` Matias Bjørling
2014-05-30 14:54 ` Matthew Wilcox
2014-05-30 14:54 ` Matthew Wilcox
2014-05-30 15:00 ` Matthew Wilcox
2014-05-30 15:00 ` Matthew Wilcox
2014-05-30 19:46 ` Jens Axboe
2014-05-30 19:46 ` Jens Axboe
2014-05-30 16:48 ` Keith Busch
2014-05-30 16:48 ` Keith Busch
2014-05-30 19:33 ` Matias Bjorling
2014-05-30 19:33 ` Matias Bjorling
2014-05-30 16:58 ` Matthew Wilcox
2014-05-30 16:58 ` Matthew Wilcox
2014-06-02 10:08 ` Christoph Hellwig
2014-06-02 10:08 ` Christoph Hellwig
2014-06-02 11:46 ` Matias Bjørling
2014-06-02 11:46 ` Matias Bjørling
2014-06-02 9:42 ` [PATCH v4] " Christoph Hellwig
2014-06-02 9:42 ` Christoph Hellwig
2014-06-02 10:31 ` Matias Bjørling [this message]
2014-06-02 10:31 ` Matias Bjørling
2014-06-02 10:11 ` Christoph Hellwig
2014-06-02 10:11 ` Christoph Hellwig
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=538C529F.1080707@bjorling.me \
--to=m@bjorling.me \
/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.