From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] nvme: move reset workqueue handling to common code
Date: Thu, 8 Jun 2017 08:53:44 -0600 [thread overview]
Message-ID: <bbdd175f-2d37-e0f5-2004-705122b399d9@kernel.dk> (raw)
In-Reply-To: <20170608130836.31891-1-hch@lst.de>
On 06/08/2017 07:08 AM, Christoph Hellwig wrote:
> This moves the nvme_reset function from the PCIe driver to common code,
> renaming it to nvme_reset_ctrl in the process. Additionally a new
> helper nvme_reset_ctrl_sync is added for the case where we want to
> wait for the reset. To facilitate that the reset_work work structure is
> move to the common nvme_ctrl structure and the ->reset_ctrl method is
> removed. For now the drivers initialize the reset_work with their own
> callback, but longer term we should move to callouts for specific
> parts of the reset process and move even more code to the core.
Nice cleanup.
Reviewed-by: Jens Axboe <axboe at kernel.dk>
--
Jens Axboe
next prev parent reply other threads:[~2017-06-08 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 13:08 [PATCH] nvme: move reset workqueue handling to common code Christoph Hellwig
2017-06-08 14:53 ` Jens Axboe [this message]
2017-06-08 16:29 ` 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=bbdd175f-2d37-e0f5-2004-705122b399d9@kernel.dk \
--to=axboe@kernel.dk \
/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