Re: [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock

To: Logan Gunthorpe <logang@xxxxxxxxxxxx>, Keith Busch <kbusch@xxxxxxxxxx>
Subject: Re: [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock
From: Sagi Grimberg <sagi@xxxxxxxxxxx>
Date: Thu, 13 Aug 2020 23:04:38 -0700
Cc: Jens Axboe <axboe@xxxxxxxxx>, Keith Busch <keith.busch@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>
In-reply-to: <829bed01-44c9-cac7-eb1b-9d1ccca7fd47@deltatee.com>
References: <20200812232444.18310-1-logang@deltatee.com> <20200813003200.GA1640756@dhcp-10-100-145-180.wdl.wdc.com> <829bed01-44c9-cac7-eb1b-9d1ccca7fd47@deltatee.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

There's an unrelated whitespace change in nvme_init_identify().
Otherwise, looks fine.


Oops, sorry. can this be fixed up when it's merged?


Fixed and queued.

References:
- [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock
  - From: Logan Gunthorpe
- Re: [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock
  - From: Keith Busch
- Re: [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock
  - From: Logan Gunthorpe