In the declaration of the structure "core_quirks[]", in the comment
referred to the devices "Kioxia CD6-V Series / HPE PE8030", the
parameter "default_ps_max_latency_us" is reported in a wrong way:

nvme_core.default_ps_max_latency=0

The correct form is, instead:

nvme_core.default_ps_max_latency_us=0

Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
---
 drivers/nvme/host/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 766e9cc4ffca..ac5a7d9781f5 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -3013,7 +3013,7 @@ static const struct nvme_core_quirk_entry core_quirks[] = {
 		 *
 		 * The device is left in a state where it is also not possible
 		 * to use "nvme set-feature" to disable APST, but booting with
-		 * nvme_core.default_ps_max_latency=0 works.
+		 * nvme_core.default_ps_max_latency_us=0 works.
 		 */
 		.vid = 0x1e0f,
 		.mn = "KCD6XVUL6T40",
-- 
2.43.0

On Wed, Apr 08, 2026 at 02:45:22PM +0200, Flavio Suligoi wrote:
> In the declaration of the structure "core_quirks[]", in the comment
> referred to the devices "Kioxia CD6-V Series / HPE PE8030", the
> parameter "default_ps_max_latency_us" is reported in a wrong way:

Thanks, applied to nvme-7.1.

On Wed, Apr 08, 2026 at 02:45:22PM +0200, Flavio Suligoi wrote:
> In the declaration of the structure "core_quirks[]", in the comment
> referred to the devices "Kioxia CD6-V Series / HPE PE8030", the
> parameter "default_ps_max_latency_us" is reported in a wrong way:

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>