From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 0/2] release /dev/nvmeX if nvme_probe failed
Date: Tue, 10 Jul 2018 13:32:16 +0200 [thread overview]
Message-ID: <20180710113216.GA32688@lst.de> (raw)
In-Reply-To: <cover.1530548893.git.zhangweiping@didichuxing.com>
Jens, Keith: any opinion on these? They seems to look fine to me,
so I'd be tempted to merge them for 4.18.
On Tue, Jul 03, 2018@12:35:07AM +0800, Weiping Zhang wrote:
>
> Changes since V1:
> * drop patch of remove whitespace
> * release iomap and prp_pools in nvme_pci_free_ctrl
> * direct use nvme_put_ctrl to release resource if failed after
> nvme_init_ctrl in nvme_probe.
>
> Weiping Zhang (2):
> nvme-pci: release iomap and prp_pools in nvme_pci_free_ctrl
> nvme-pci: release nvme_ctrl if failed to alloc memory in nvme_probe
>
> drivers/nvme/host/pci.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> --
> 2.14.1
---end quoted text---
next prev parent reply other threads:[~2018-07-10 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 16:35 [PATCH v2 0/2] release /dev/nvmeX if nvme_probe failed Weiping Zhang
2018-07-02 16:35 ` [PATCH v2 1/2] nvme-pci: release iomap and prp_pools in nvme_pci_free_ctrl Weiping Zhang
2018-07-10 14:45 ` Keith Busch
2018-07-11 13:38 ` Weiping Zhang
2018-07-11 15:03 ` Keith Busch
2018-07-11 15:38 ` Weiping Zhang
2018-07-11 16:04 ` Keith Busch
2018-07-02 16:35 ` [PATCH v2 2/2] nvme-pci: release nvme_ctrl if failed to alloc memory in nvme_probe Weiping Zhang
2018-07-10 14:45 ` Keith Busch
2018-07-10 11:32 ` Christoph Hellwig [this message]
2018-07-10 14:09 ` [PATCH v2 0/2] release /dev/nvmeX if nvme_probe failed Jens Axboe
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=20180710113216.GA32688@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 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.