From: Bart Van Assche <bvanassche@acm.org>
To: "Asutosh Das (asd)" <asutoshd@codeaurora.org>,
cang@codeaurora.org, martin.petersen@oracle.com,
stern@rowland.harvard.edu
Cc: linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/2] Fix deadlock in ufs
Date: Mon, 1 Feb 2021 12:27:33 -0800 [thread overview]
Message-ID: <cbc1ea4a-e44c-9d7b-a6f6-73959dd8afb5@acm.org> (raw)
In-Reply-To: <84a182cc-de9c-4d6d-2193-3a44e4c88c8b@codeaurora.org>
On 2/1/21 12:11 PM, Asutosh Das (asd) wrote:
> Please can you take a look at this series.
> Please let me know if you've any better suggestions for this.
Hi Asutosh,
Against which kernel version has this patch series been prepared and
tested? Have you noticed the following patch series that went into
v5.11-rc1:
https://lore.kernel.org/linux-scsi/20201209052951.16136-1-bvanassche@acm.org/
?
Thanks,
Bart.
next prev parent reply other threads:[~2021-02-01 20:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 4:00 [RFC PATCH v1 0/2] Fix deadlock in ufs Asutosh Das
2021-01-28 3:26 ` [RFC PATCH v2 " Asutosh Das
2021-01-27 4:00 ` [RFC PATCH v1 1/2] block: bsg: resume scsi device before accessing Asutosh Das
2021-01-27 7:09 ` Avri Altman
2021-01-27 7:59 ` Can Guo
2021-01-27 8:53 ` Can Guo
2021-02-07 2:23 ` Bart Van Assche
2021-01-27 4:00 ` [RFC PATCH v1 2/2] scsi: ufs: Fix deadlock while suspending ufs host Asutosh Das
2021-01-27 15:22 ` [RFC PATCH v1 0/2] Fix deadlock in ufs Bjorn Andersson
2021-01-27 16:16 ` Asutosh Das
2021-01-27 19:36 ` Bjorn Andersson
2021-01-28 2:47 ` Can Guo
2021-01-28 3:26 ` [RFC PATCH v2 1/2] block: bsg: resume platform device before accessing Asutosh Das
2021-01-28 3:26 ` [RFC PATCH v2 2/2] scsi: ufs: Fix deadlock while suspending ufs host Asutosh Das
2021-01-28 12:21 ` Avri Altman
2021-01-28 16:39 ` Asutosh Das
2021-01-28 9:33 ` [RFC PATCH v2 0/2] Fix deadlock in ufs Avri Altman
2021-01-28 17:19 ` Asutosh Das
2021-02-01 20:11 ` Asutosh Das (asd)
2021-02-01 20:27 ` Bart Van Assche [this message]
2021-02-01 21:48 ` Alan Stern
2021-02-02 20:52 ` Asutosh Das
2021-02-02 22:05 ` Alan Stern
2021-02-04 0:13 ` Asutosh Das
2021-02-04 19:48 ` Alan Stern
2021-02-04 21:14 ` Asutosh Das
2021-02-05 7:56 ` Avri Altman
2021-02-05 16:11 ` Asutosh Das
2021-02-06 2:37 ` Asutosh Das
2021-02-06 19:24 ` Avri Altman
2021-02-08 16:24 ` Asutosh Das
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=cbc1ea4a-e44c-9d7b-a6f6-73959dd8afb5@acm.org \
--to=bvanassche@acm.org \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stern@rowland.harvard.edu \
/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.