[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<BY5PR04MB684919E8FED440576C3A52F4BC5FA@BY5PR04MB6849.namprd04.prod.outlook.com>
Date: Wed, 23 Jul 2025 18:27:11 +0000
From: Kamaljit Singh <Kamaljit.Singh1@....com>
To: hch <hch@....de>
CC: hch <hch@....de>, "kbusch@...nel.org" <kbusch@...nel.org>,
"axboe@...nel.dk" <axboe@...nel.dk>, "sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"cassel@...nel.org" <cassel@...nel.org>, "dlemoal@...nel.org"
<dlemoal@...nel.org>
Subject: Re: [PATCH v4 2/2] nvme: prevent admin controller from smart log
fetch (LID 2)
From: hch <hch@....de>
Date: Tuesday, July 22, 2025 at 23:11
>> By "let's leave this in", I thought you were referring to my patch. But now that I re-read
>> it, seems like by "failing a get_log page is fine" you probably meant to let the driver
>> issue a get_log for LID=2 and fail.
>
>Yes.
>> Process wise, can you ignore this 2/2 patch and we call this patch-set done?
>
>That's what I've done. Patch 1 is queued up in the nvme-6.17 branch.
Yes, I already pulled it. Thank you Christoph!
-Kamaljit
Powered by blists - more mailing lists