From: Jianchao Wang <jianchao.w.wang@oracle.com>
To: keith.busch@intel.com, axboe@fb.com, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCHSET] nvme-pci: sort out nvme initialization procedure in nvme_rest_work
Date: Wed, 3 Jan 2018 07:56:07 +0800 [thread overview]
Message-ID: <1514937370-4805-1-git-send-email-jianchao.w.wang@oracle.com> (raw)
Hello
This patchset is to sort out the nvme initialization procedure in
nvme_reset_work. There is no functional changes in it. Add two new
helper interfaces nvme_pci_pre_init and nvme_pci_post_init to package
the nvme specific initialization work before configuring adminq and
after getting identify information. Then nvme_pci_enable,
nvme_pci_configure_admin_queue and nvme_reset_work could be clearer.
Change functions' name, nvme_pci_configure_admin_queue and
nvme_alloc_admin_tags to nvme_pci_setup_adminq and
nvme_pci_start_adminq to make it more readable.
Jianchao Wang (3)
0001-nvme-pci-add-nvme_pci_pre_init.patch
0002-nvme-pci-change-the-name-of-functions-corresponding-.patch
0003-nvme-pci-add-nvme_pci_post_init.patch
drivers/nvme/host/pci.c | 211 ++++++++++++++++++++++++++----------------------
1 file changed, 115 insertions(+), 96 deletions(-)
Thanks
Jianchao
next reply other threads:[~2018-01-02 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 23:56 Jianchao Wang [this message]
2018-01-02 23:56 ` [PATCH 1/3] nvme-pci: add nvme_pci_pre_init Jianchao Wang
2018-01-02 23:56 ` [PATCH 2/3] nvme-pci: change the name of functions corresponding to setup adminq Jianchao Wang
2018-01-02 23:56 ` [PATCH 3/3] nvme-pci: add nvme_pci_post_init Jianchao Wang
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=1514937370-4805-1-git-send-email-jianchao.w.wang@oracle.com \
--to=jianchao.w.wang@oracle.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).