From: Christoph Hellwig <hch@lst.de>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
keith.busch@intel.com, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@lightbits.io, ming.l@ssi.samsung.com
Subject: Re: [PATCH 01/11] Revert "blk-mq: add blk_mq_alloc_request_hctx"
Date: Wed, 8 Jun 2016 16:10:19 +0200 [thread overview]
Message-ID: <20160608141019.GB1020@lst.de> (raw)
In-Reply-To: <x49mvmv235d.fsf@segfault.boston.devel.redhat.com>
On Wed, Jun 08, 2016 at 09:58:38AM -0400, Jeff Moyer wrote:
> Christoph Hellwig <hch@lst.de> writes:
>
> > Just for book keeping. The next patch brings it back with some changes.
>
> That's a strange thing to do, and breaks bisectability. Why not just
> update the function?
Because it's just an updated to a not yet applied series. The idea is
that Jens could just take patch 2 if we get a positive review or two for
it.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 01/11] Revert "blk-mq: add blk_mq_alloc_request_hctx"
Date: Wed, 8 Jun 2016 16:10:19 +0200 [thread overview]
Message-ID: <20160608141019.GB1020@lst.de> (raw)
In-Reply-To: <x49mvmv235d.fsf@segfault.boston.devel.redhat.com>
On Wed, Jun 08, 2016@09:58:38AM -0400, Jeff Moyer wrote:
> Christoph Hellwig <hch at lst.de> writes:
>
> > Just for book keeping. The next patch brings it back with some changes.
>
> That's a strange thing to do, and breaks bisectability. Why not just
> update the function?
Because it's just an updated to a not yet applied series. The idea is
that Jens could just take patch 2 if we get a positive review or two for
it.
next prev parent reply other threads:[~2016-06-08 14:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 12:30 NVMe over Fabrics: updates for req_op changes and misc fixes Christoph Hellwig
2016-06-08 12:30 ` Christoph Hellwig
2016-06-08 12:30 ` [PATCH 01/11] Revert "blk-mq: add blk_mq_alloc_request_hctx" Christoph Hellwig
2016-06-08 12:30 ` Christoph Hellwig
2016-06-08 13:58 ` Jeff Moyer
2016-06-08 13:58 ` Jeff Moyer
2016-06-08 14:10 ` Christoph Hellwig [this message]
2016-06-08 14:10 ` Christoph Hellwig
2016-06-08 14:13 ` Jeff Moyer
2016-06-08 14:13 ` Jeff Moyer
2016-06-08 12:30 ` [PATCH 02/11] blk-mq: add blk_mq_alloc_request_hctx Christoph Hellwig
2016-06-08 12:30 ` Christoph Hellwig
2016-06-08 13:43 ` Sagi Grimberg
2016-06-08 13:43 ` Sagi Grimberg
2016-06-08 12:30 ` [PATCH 03/11] nvme_rdma: update for req_op changes Christoph Hellwig
2016-06-08 12:30 ` Christoph Hellwig
2016-06-08 13:44 ` Sagi Grimberg
2016-06-08 13:44 ` Sagi Grimberg
2016-06-08 22:03 ` Ming Lin
2016-06-08 22:03 ` Ming Lin
2016-06-08 12:30 ` [PATCH 04/11] nvmet: " Christoph Hellwig
2016-06-08 12:30 ` Christoph Hellwig
2016-06-08 13:44 ` Sagi Grimberg
2016-06-08 13:44 ` Sagi Grimberg
2016-06-14 14:27 ` Christoph Hellwig
2016-06-14 14:27 ` Christoph Hellwig
2016-06-08 12:31 ` [PATCH 05/11] nvme-loop: set SGL flag on AER Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 12:31 ` [PATCH 06/11] nvme-rdma: " Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 12:31 ` [PATCH 07/11] nvmet: fix 64-bit division in nvmet_set_features Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 13:53 ` Sagi Grimberg
2016-06-08 13:53 ` Sagi Grimberg
2016-06-08 12:31 ` [PATCH 08/11] nvmet: fix eno.cocci warnings Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 22:09 ` Ming Lin
2016-06-08 22:09 ` Ming Lin
2016-06-08 12:31 ` [PATCH 09/11] nvmet-rdma: check for a valid adrfam Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 12:31 ` [PATCH 10/11] nvme: keep alive should use any queue Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 13:54 ` Sagi Grimberg
2016-06-08 13:54 ` Sagi Grimberg
2016-06-08 12:31 ` [PATCH 11/11] nvme-fabrics: pass non-blocking flag to connect request allocation Christoph Hellwig
2016-06-08 12:31 ` Christoph Hellwig
2016-06-08 13:55 ` Sagi Grimberg
2016-06-08 13:55 ` Sagi Grimberg
2016-06-08 14:09 ` Christoph Hellwig
2016-06-08 14:09 ` Christoph Hellwig
2016-06-08 22:21 ` NVMe over Fabrics: updates for req_op changes and misc fixes Ming Lin
2016-06-08 22:21 ` Ming Lin
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=20160608141019.GB1020@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.l@ssi.samsung.com \
--cc=sagi@lightbits.io \
/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.