From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: jejb@linux.ibm.com, alim.akhtar@samsung.com, avri.altman@wdc.com,
Stanley Chu <stanley.chu@mediatek.com>,
linux-scsi@vger.kernel.org
Cc: bvanassche@acm.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
andy.teng@mediatek.com, cc.chou@mediatek.com,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, cang@codeaurora.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, matthias.bgg@gmail.com,
asutoshd@codeaurora.org, peter.wang@mediatek.com,
chaotian.jing@mediatek.com, beanhuo@micron.com
Subject: Re: [PATCH v2] scsi: ufs: Disable WriteBooster capability in non-supported UFS device
Date: Fri, 26 Jun 2020 23:09:25 -0400 [thread overview]
Message-ID: <159322718420.11145.18067065778687552607.b4-ty@oracle.com> (raw)
In-Reply-To: <20200625030430.25048-1-stanley.chu@mediatek.com>
On Thu, 25 Jun 2020 11:04:30 +0800, Stanley Chu wrote:
> If UFS device is not qualified to enter the detection of WriteBooster
> probing by disallowed UFS version or device quirks, then WriteBooster
> capability in host shall be disabled to prevent any WriteBooster
> operations in the future.
Applied to 5.9/scsi-queue, thanks!
[1/1] scsi: ufs: Disable WriteBooster capability for non-supported UFS devices
https://git.kernel.org/mkp/scsi/c/a7f1e69d4974
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-06-27 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 3:04 [PATCH v2] scsi: ufs: Disable WriteBooster capability in non-supported UFS device Stanley Chu
2020-06-25 10:26 ` [EXT] " Bean Huo (beanhuo)
2020-06-27 3:09 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-24 7:41 Stanley Chu
2020-06-24 7:45 ` Avri Altman
2020-06-30 17:32 ` Asutosh Das (asd)
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=159322718420.11145.18067065778687552607.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--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).