From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Tomas Henzl <thenzl@redhat.com>, linux-ide@vger.kernel.org
Cc: sergei.shtylyov@gmail.com
Subject: Re: [PATCH V4] ata: libata-core: Print timeout value when internal command times
Date: Wed, 17 Aug 2022 09:43:07 -0700 [thread overview]
Message-ID: <e6c84c32-6737-86e4-1e3c-8828864fad04@opensource.wdc.com> (raw)
In-Reply-To: <20220810175909.14485-1-thenzl@redhat.com>
On 2022/08/10 10:59, Tomas Henzl wrote:
> Printing the timeout value may help in troubleshooting failures.
>
> Signed-off-by: David Milburn <dmilburn@redhat.com>
> Signed-off-by: Tomas Henzl <thenzl@redhat.com>
> ---
> V4: a whitespace change
> a switch from an an infinitive to an -ing form in the body
> a fix to the title prefix
> V3: rewording subject and description, no functional change
> V2: timeout changed to unsigned int as in for-next
> ---
> drivers/ata/libata-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 826d41f341e4..9478194740e0 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -1578,8 +1578,8 @@ static unsigned ata_exec_internal_sg(struct ata_device *dev,
> else
> ata_qc_complete(qc);
>
> - ata_dev_warn(dev, "qc timeout (cmd 0x%x)\n",
> - command);
> + ata_dev_warn(dev, "qc timeout after %u msecs (cmd 0x%x)\n",
> + timeout, command);
> }
>
> spin_unlock_irqrestore(ap->lock, flags);
Applied to for-6.1. Thanks !
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-08-17 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 17:59 [PATCH V4] ata: libata-core: Print timeout value when internal command times Tomas Henzl
2022-08-17 16:43 ` Damien Le Moal [this message]
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=e6c84c32-6737-86e4-1e3c-8828864fad04@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=sergei.shtylyov@gmail.com \
--cc=thenzl@redhat.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