From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: stanley.chu@mediatek.com, bvanassche@acm.org,
tomas.winkler@intel.com, cang@codeaurora.org,
avri.altman@wdc.com, asutoshd@codeaurora.org,
Bean Huo <huobean@gmail.com>,
jejb@linux.ibm.com, beanhuo@micron.com, alim.akhtar@samsung.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 0/2] scsi: ufs: two fixups of ufshcd_abort()
Date: Mon, 17 Aug 2020 23:12:26 -0400 [thread overview]
Message-ID: <159772029326.19587.13319744810377565226.b4-ty@oracle.com> (raw)
In-Reply-To: <20200811141859.27399-1-huobean@gmail.com>
On Tue, 11 Aug 2020 16:18:57 +0200, Bean Huo wrote:
> Changelog:
>
> v1 - v2:
> 1. add patch [1/2], which is from Stanley Chu <stanley.chu@mediatek.com>
> 2. change goto command in patch [2/2], let it goto cleanup flow
>
> Bean Huo (1):
> scsi: ufs: no need to send one Abort Task TM in case the task in DB
> was cleared
>
> [...]
Applied to 5.9/scsi-fixes, thanks!
[1/2] scsi: ufs: Clean up completed request without interrupt notification
https://git.kernel.org/mkp/scsi/c/b10178ee7fa8
[2/2] scsi: ufs: No need to send Abort Task if the task in DB was cleared
https://git.kernel.org/mkp/scsi/c/d87a1f6d021f
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-08-18 3:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 14:18 [PATCH v2 0/2] scsi: ufs: two fixups of ufshcd_abort() Bean Huo
2020-08-11 14:18 ` [PATCH v2 1/2] scsi: ufs: Cleanup completed request without interrupt notification Bean Huo
2020-08-12 12:47 ` Stanley Chu
2020-08-12 14:42 ` Bean Huo
2020-08-13 11:05 ` Avri Altman
2020-08-11 14:18 ` [PATCH v2 2/2] scsi: ufs: no need to send one Abort Task TM in case the task in DB was cleared Bean Huo
2020-08-14 9:27 ` Can Guo
2020-08-16 1:54 ` Stanley Chu
2020-08-18 3:12 ` 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=159772029326.19587.13319744810377565226.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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.