From: Stanley Chu <stanley.chu@mediatek.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] ufs: Fix a race between the interrupt handler and the reset handler
Date: Tue, 14 Jun 2022 10:23:06 +0800 [thread overview]
Message-ID: <c16ed22c8d23b9da65e3695dab70a03812851678.camel@mediatek.com> (raw)
In-Reply-To: <20220613214442.212466-1-bvanassche@acm.org>
Hi Bart,
I am not sure if this series could solve the racing you met.
However this series looks good to me.
Reviewed-by: Stanley Chu <stanley.chu@mediatek.com>
On Mon, 2022-06-13 at 14:44 -0700, Bart Van Assche wrote:
> Hi Martin,
>
> This patch series is version two of a fix between the UFS interrupt
> handler and
> reset handlers. Please consider this patch series for kernel v5.20.
>
> Changes compared to v1:
> - Converted a single patch into three patches.
> - Modified patch 3/3 such that only cleared requests are completed.
>
> Bart Van Assche (3):
> scsi: ufs: Simplify ufshcd_clear_cmd()
> scsi: ufs: Support clearing multiple commands at once
> scsi: ufs: Fix a race between the interrupt handler and the reset
> handler
>
> drivers/ufs/core/ufshcd.c | 76 ++++++++++++++++++++++++-------------
> --
> 1 file changed, 48 insertions(+), 28 deletions(-)
>
next prev parent reply other threads:[~2022-06-14 2:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 21:44 [PATCH v2 0/3] ufs: Fix a race between the interrupt handler and the reset handler Bart Van Assche
2022-06-13 21:44 ` [PATCH v2 1/3] scsi: ufs: Simplify ufshcd_clear_cmd() Bart Van Assche
2022-06-13 21:44 ` [PATCH v2 2/3] scsi: ufs: Support clearing multiple commands at once Bart Van Assche
2022-06-13 21:44 ` [PATCH v2 3/3] scsi: ufs: Fix a race between the interrupt handler and the reset handler Bart Van Assche
2022-06-14 2:23 ` Stanley Chu [this message]
2022-06-14 6:51 ` [PATCH v2 0/3] " Adrian Hunter
2022-06-17 2:20 ` Martin K. Petersen
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=c16ed22c8d23b9da65e3695dab70a03812851678.camel@mediatek.com \
--to=stanley.chu@mediatek.com \
--cc=adrian.hunter@intel.com \
--cc=bvanassche@acm.org \
--cc=jaegeuk@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.