From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>,
alim.akhtar@samsung.com, linux-scsi@vger.kernel.org,
bvanassche@acm.org, avri.altman@wdc.com, jejb@linux.ibm.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
asutoshd@codeaurora.org, chaotian.jing@mediatek.com,
linux-kernel@vger.kernel.org, chun-hung.wu@mediatek.com,
cc.chou@mediatek.com, kuohong.wang@mediatek.com,
andy.teng@mediatek.com, peter.wang@mediatek.com,
linux-mediatek@lists.infradead.org, beanhuo@micron.com,
cang@codeaurora.org
Subject: Re: [PATCH v1] scsi: ufs-mediatek: Prevent LPM operation on undeclared VCC
Date: Wed, 29 Jul 2020 00:10:39 -0400 [thread overview]
Message-ID: <159599579269.11289.6290519953354146093.b4-ty@oracle.com> (raw)
In-Reply-To: <20200724141627.20094-1-stanley.chu@mediatek.com>
On Fri, 24 Jul 2020 22:16:27 +0800, Stanley Chu wrote:
> In some platforms, VCC regulator may not be declared in device tree
> to keep itself "always-on". In this case, hba->vreg_info.vcc is NULL
> and shall not be operated during any flow.
>
> Prevent possible NULL hba->vreg_info.vcc access in LPM mode by checking
> if it is valid first.
Applied to 5.9/scsi-queue, thanks!
[1/1] scsi: ufs-mediatek: Prevent LPM operation on undeclared VCC
https://git.kernel.org/mkp/scsi/c/0255b1e3d849
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-07-29 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 14:16 [PATCH v1] scsi: ufs-mediatek: Prevent LPM operation on undeclared VCC Stanley Chu
2020-07-27 10:56 ` Avri Altman
2020-07-29 4:10 ` 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=159599579269.11289.6290519953354146093.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).