Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Guixin Liu" <kanie@linux.alibaba.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH 5/9] nvme: drop unreachable "off" case in reconnect_delay_show()
Date: Thu, 05 Nov 2026 02:20:34 +0000	[thread overview]
Message-ID: <sashiko-outbox-198452@kernel.org> (raw)
In-Reply-To: <20261105021051.1667222-6-kanie@linux.alibaba.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] nvme: Documentation/ABI/stable/sysfs-nvme out of sync for reconnect_delay
--

commit 0bdac7a94ae088ab38d8d6006c42a68c7d0447dc
Author: Guixin Liu <kanie@linux.alibaba.com>

nvme: drop unreachable "off" case in reconnect_delay_show()

This commit removes the check for ctrl->opts->reconnect_delay == -1 in
nvme_ctrl_reconnect_delay_show() so that reading reconnect_delay no longer
emits "off".

> diff --git a/drivers/nvme/host/sysfs.c b/drivers/nvme/host/sysfs.c
> index 10018c6356b62..3724b5ce03a07 100644
> --- a/drivers/nvme/host/sysfs.c
> +++ b/drivers/nvme/host/sysfs.c
> @@ -618,8 +618,6 @@ static ssize_t nvme_ctrl_reconnect_delay_show(struct device *dev,
>  {
>  	struct nvme_ctrl *ctrl = dev_get_drvdata(dev);
>  
> -	if (ctrl->opts->reconnect_delay == -1)
> -		return sysfs_emit(buf, "off\n");
>  	return sysfs_emit(buf, "%d\n", ctrl->opts->reconnect_delay);

[Severity: Low]
With this branch removed from nvme_ctrl_reconnect_delay_show() in
drivers/nvme/host/sysfs.c, reading /sys/class/nvme/nvmeX/reconnect_delay
never outputs "off". However, Documentation/ABI/stable/sysfs-nvme still
states:

		reconnect_delay: Shows or sets the reconnect delay in
		seconds. Reading returns the delay value, or "off" if
		disabled.

Should Documentation/ABI/stable/sysfs-nvme be updated to drop the "off"
description as well?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261105021051.1667222-1-kanie@linux.alibaba.com?part=5


  reply	other threads:[~2026-11-05  2:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  2:10 [PATCH 0/9] nvme: dead code cleanups Guixin Liu
2026-11-05  2:10 ` [PATCH 1/9] nvme-pci: remove write-only NVMEQ_DELETE_ERROR flag Guixin Liu
2026-11-05  2:10 ` [PATCH 2/9] nvme-fc: remove dead seqno field in nvme_fc_queue Guixin Liu
2026-11-05  2:10 ` [PATCH 3/9] nvme-auth: remove dead entry field in nvme_dhchap_queue_context Guixin Liu
2026-11-05  2:10 ` [PATCH 4/9] nvme-fabrics: remove dead hostnqn already-assigned check Guixin Liu
2026-11-05  2:10 ` [PATCH 5/9] nvme: drop unreachable "off" case in reconnect_delay_show() Guixin Liu
2026-11-05  2:20   ` sashiko-bot [this message]
2026-11-05  2:10 ` [PATCH 6/9] nvmet-fc: remove dead fields in nvmet_fc_ls_iod and nvmet_fc_tgt_queue Guixin Liu
2026-11-05  2:10 ` [PATCH 7/9] nvmet: remove unreachable "pcie" entry from the address family map Guixin Liu
2026-11-05  2:10 ` [PATCH 8/9] nvmet: passthru: remove unreachable break statements Guixin Liu
2026-11-05  2:10 ` [PATCH 9/9] nvmet-pci-epf: don't drain the never-populated SQ list Guixin Liu

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=sashiko-outbox-198452@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kanie@linux.alibaba.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox