From: Hannes Reinecke <hare@suse.de>
To: Niklas Cassel <cassel@kernel.org>, Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata: Fix NCQ Non-Data log not supported print
Date: Mon, 17 Mar 2025 12:38:35 +0100 [thread overview]
Message-ID: <be6ed8ef-4f34-45a1-a18a-9504d0a7b809@suse.de> (raw)
In-Reply-To: <20250317111754.1666084-2-cassel@kernel.org>
On 3/17/25 12:17, Niklas Cassel wrote:
> Currently, both ata_dev_config_ncq_send_recv() - which checks for NCQ
> Send/Recv Log (Log Address 13h) and ata_dev_config_ncq_non_data() -
> which checks for NCQ Non-Data Log (Log Address 12h), uses the same
> print when the log is not supported:
>
> "NCQ Send/Recv Log not supported"
>
> This seems like a copy paste error, since NCQ Non-Data Log is actually
> a separate log.
>
> Fix the print the reference the correct log.
>
> Fixes: 284b3b77ea88 ("libata: NCQ encapsulation for ZAC MANAGEMENT OUT")
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
> drivers/ata/libata-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 193fc3942fd3a..e17e16706db70 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -2274,7 +2274,7 @@ static void ata_dev_config_ncq_non_data(struct ata_device *dev)
>
> if (!ata_log_supported(dev, ATA_LOG_NCQ_NON_DATA)) {
> ata_dev_warn(dev,
> - "NCQ Send/Recv Log not supported\n");
> + "NCQ Non-Data Log not supported\n");
> return;
> }
> err_mask = ata_read_log_page(dev, ATA_LOG_NCQ_NON_DATA,
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-03-17 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 11:17 [PATCH] ata: libata: Fix NCQ Non-Data log not supported print Niklas Cassel
2025-03-17 11:38 ` Hannes Reinecke [this message]
2025-03-18 5:18 ` Damien Le Moal
2025-03-18 8:05 ` Niklas Cassel
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=be6ed8ef-4f34-45a1-a18a-9504d0a7b809@suse.de \
--to=hare@suse.de \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
/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