Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v2] nvme: Use spin_lock_irq() when taking the ctrl->lock
To:     Logan Gunthorpe <logang@deltatee.com>,
        Keith Busch <kbusch@kernel.org>
Cc:     Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@wdc.com>,
        linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
        linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
References: <20200812232444.18310-1-logang@deltatee.com>
 <20200813003200.GA1640756@dhcp-10-100-145-180.wdl.wdc.com>
 <829bed01-44c9-cac7-eb1b-9d1ccca7fd47@deltatee.com>
From:   Sagi Grimberg <sagi@grimberg.me>
Message-ID: <498ea4cf-1edd-e50e-35aa-b5529616337b@grimberg.me>
Date:   Thu, 13 Aug 2020 23:04:38 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <829bed01-44c9-cac7-eb1b-9d1ccca7fd47@deltatee.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


>> 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.