From: hch@lst.de (Christoph Hellwig)
Subject: update ->init_request and ->exit_request prototypes
Date: Fri, 28 Apr 2017 16:53:00 +0200 [thread overview]
Message-ID: <20170428145300.GA1776@lst.de> (raw)
In-Reply-To: <20170427174501.18965-1-hch@lst.de>
On Thu, Apr 27, 2017@07:44:56PM +0200, Christoph Hellwig wrote:
> Hi Jens,
>
> this series (against for-4.12/post-merge) updates the blk-mq
> ->init_request and ->exit request methods to drop a now harmful
> parameter, and update one to pass a little more information. It
> then cleans up the nvme drivers based on that.
Turns out that while Jeff was right that this won't work against
for-4.12/post-merge, it applies without fuzz and works fine against
for-next. Sorry for the confusion.
next prev parent reply other threads:[~2017-04-28 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 17:44 update ->init_request and ->exit_request prototypes Christoph Hellwig
2017-04-27 17:44 ` [PATCH 1/5] blk-mq: " Christoph Hellwig
2017-04-27 18:20 ` Jeff Moyer
2017-04-28 14:09 ` Christoph Hellwig
2017-04-28 14:19 ` Jens Axboe
2017-04-28 14:20 ` Jens Axboe
2017-04-28 14:24 ` Christoph Hellwig
2017-04-28 14:27 ` Jeff Moyer
2017-04-27 17:44 ` [PATCH 2/5] nvme-pci: merge init_request methods Christoph Hellwig
2017-04-27 17:44 ` [PATCH 3/5] nvme-rdma: merge init_request and exit_request methods Christoph Hellwig
2017-04-27 17:45 ` [PATCH 4/5] nvme-fc: merge init_request methods Christoph Hellwig
2017-04-27 17:45 ` [PATCH 5/5] nvme-loop: " Christoph Hellwig
2017-04-28 14:53 ` Christoph Hellwig [this message]
2017-05-03 7:53 ` update ->init_request and ->exit_request prototypes 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=20170428145300.GA1776@lst.de \
--to=hch@lst.de \
/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