From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Israel Rukshin <israelr@mellanox.com>,
James Smart <james.smart@broadcom.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@fb.com>, Keith Busch <kbusch@kernel.org>,
Max Gurtovoy <maxg@mellanox.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme: do not call del_gendisk() on a disk that was never added
Date: Tue, 9 Jun 2020 15:44:43 +0200 [thread overview]
Message-ID: <20200609134443.GA10030@lst.de> (raw)
In-Reply-To: <20200607114520.130756-1-niklas.cassel@wdc.com>
Thanks,
applied to nvme-5.8.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
James Smart <james.smart@broadcom.com>,
Israel Rukshin <israelr@mellanox.com>,
Max Gurtovoy <maxg@mellanox.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: do not call del_gendisk() on a disk that was never added
Date: Tue, 9 Jun 2020 15:44:43 +0200 [thread overview]
Message-ID: <20200609134443.GA10030@lst.de> (raw)
In-Reply-To: <20200607114520.130756-1-niklas.cassel@wdc.com>
Thanks,
applied to nvme-5.8.
next prev parent reply other threads:[~2020-06-09 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 11:45 [PATCH] nvme: do not call del_gendisk() on a disk that was never added Niklas Cassel
2020-06-07 11:45 ` Niklas Cassel
2020-06-07 13:13 ` Max Gurtovoy
2020-06-07 13:13 ` Max Gurtovoy
2020-06-08 4:42 ` Sagi Grimberg
2020-06-08 4:42 ` Sagi Grimberg
2020-06-09 13:44 ` Christoph Hellwig [this message]
2020-06-09 13:44 ` Christoph Hellwig
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=20200609134443.GA10030@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=israelr@mellanox.com \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=niklas.cassel@wdc.com \
--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 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.