From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>, Bean Huo <huobean@gmail.com>,
Can Guo <cang@codeaurora.org>,
Stanley Chu <stanley.chu@mediatek.com>
Subject: Re: [PATCH 0/4] scsi: ufs-pci: Fixes for Intel controllers
Date: Tue, 08 Dec 2020 21:46:20 -0500 [thread overview]
Message-ID: <yq1o8j3snm2.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20201207083120.26732-1-adrian.hunter@intel.com> (Adrian Hunter's message of "Mon, 7 Dec 2020 10:31:16 +0200")
Adrian,
> Here are some small fixes / amendments.
>
> Adrian Hunter (4):
> scsi: ufs-pci: Fix restore from S4 for Intel controllers
> scsi: ufs-pci: Ensure UFS device is in PowerDown mode for suspend-to-disk ->poweroff()
> scsi: ufs-pci: Fix recovery from hibernate exit errors for Intel controllers
> scsi: ufs-pci: Enable UFSHCD_CAP_RPM_AUTOSUSPEND for Intel controllers
Applied to 5.11/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-12-09 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 8:31 [PATCH 0/4] scsi: ufs-pci: Fixes for Intel controllers Adrian Hunter
2020-12-07 8:31 ` [PATCH 1/4] scsi: ufs-pci: Fix restore from S4 " Adrian Hunter
2020-12-07 8:31 ` [PATCH 2/4] scsi: ufs-pci: Ensure UFS device is in PowerDown mode for suspend-to-disk ->poweroff() Adrian Hunter
2020-12-07 8:31 ` [PATCH 3/4] scsi: ufs-pci: Fix recovery from hibernate exit errors for Intel controllers Adrian Hunter
2020-12-07 8:31 ` [PATCH 4/4] scsi: ufs-pci: Enable UFSHCD_CAP_RPM_AUTOSUSPEND " Adrian Hunter
2020-12-09 2:46 ` 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=yq1o8j3snm2.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--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 \
/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).