From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <avri.altman@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH] scsi: ufs: Do not open code read_poll_timeout
Date: Thu, 03 Oct 2024 21:49:58 -0400 [thread overview]
Message-ID: <yq1ed4w3adu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240919112442.48491-1-avri.altman@wdc.com> (Avri Altman's message of "Thu, 19 Sep 2024 14:24:42 +0300")
Avri,
> ufshcd_wait_for_register practically does just that - replace with
> read_poll_timeout.
Applied to 6.13/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2024-10-04 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 11:24 [PATCH] scsi: ufs: Do not open code read_poll_timeout Avri Altman
2024-09-20 18:23 ` Bart Van Assche
2024-09-20 19:00 ` Avri Altman
2024-09-20 19:38 ` Bart Van Assche
2024-09-20 19:38 ` Bart Van Assche
2024-10-04 1:49 ` Martin K. Petersen [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=yq1ed4w3adu.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).