Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Shawn Lin <shawn.lin@rock-chips.com>,
	"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: core: Fix stale comment in ufshcd_mcq_config_nr_queues()
Date: Fri, 16 Oct 2026 11:18:37 -0700	[thread overview]
Message-ID: <9727e883-c2fa-462a-ab30-481a0e4f77c4@acm.org> (raw)
In-Reply-To: <1792133053-143069-1-git-send-email-shawn.lin@rock-chips.com>

On 10/15/26 11:44 PM, Shawn Lin wrote:
> diff --git a/drivers/ufs/core/ufs-mcq.c b/drivers/ufs/core/ufs-mcq.c
> index df293b6..15401e1 100644
> --- a/drivers/ufs/core/ufs-mcq.c
> +++ b/drivers/ufs/core/ufs-mcq.c
> @@ -184,7 +184,7 @@ static int ufshcd_mcq_config_nr_queues(struct ufs_hba *hba)
>   
>   	/*
>   	 * Device should support at least one I/O queue to handle device
> -	 * commands via hba->dev_cmd_queue.
> +	 * commands, which cannot be handled by a poll queue.
>   	 */
>   	if (hba_maxq == poll_queues) {
>   		dev_err(hba->dev, "At least one non-poll queue required\n");

A few comments:
- "Device" in the existing comment is inaccurate since hba_maxq is a
   host controller capability rather than a UFS device property.
- At least one non-poll (HCTX_TYPE_DEFAULT) queue is required not only
   for UFS device management commands, but also for all non-polled SCSI
   commands. How about updating the comment to:
	/*
	 * At least one non-poll (HCTX_TYPE_DEFAULT) queue is required for
	 * non-polled SCSI commands and UFS device management commands.
	 */
- Please drop the Fixes: tag since this patch only updates a comment.

Thanks,

Bart.

  parent reply	other threads:[~2026-10-16 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  6:44 [PATCH] scsi: ufs: core: Fix stale comment in ufshcd_mcq_config_nr_queues() Shawn Lin
2026-10-16  8:19 ` Stanley Jhu
2026-10-16 18:18 ` Bart Van Assche [this message]
2026-10-17  0:22   ` Shawn Lin

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=9727e883-c2fa-462a-ab30-481a0e4f77c4@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=shawn.lin@rock-chips.com \
    /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