From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: devicetree@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, robh@kernel.org,
vivek.gautam@codeaurora.org, subhashj@codeaurora.org,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
evgreen@chromium.org, avri.altman@wdc.com, robh+dt@kernel.org,
linux-mediatek@lists.infradead.org, peter.wang@mediatek.com,
alim.akhtar@samsung.com, matthias.bgg@gmail.com,
sayalil@codeaurora.org, pedrom.sousa@synopsys.com,
linux-arm-kernel@lists.infradead.org, beanhuo@micron.com
Subject: Re: [PATCH 0/2] scsi: dt-bindings: ufs: Remove "<name>-fixed-regulator" property and add VCC capability on MediaTek UFS driver
Date: Wed, 03 Apr 2019 23:26:40 -0400 [thread overview]
Message-ID: <yq1imvutpqn.fsf@oracle.com> (raw)
In-Reply-To: <1553873568-9177-1-git-send-email-stanley.chu@mediatek.com> (Stanley Chu's message of "Fri, 29 Mar 2019 23:32:46 +0800")
Stanley,
> Now we can remove custom device tree property "<name>-fixed-regulator" for
> UFS because,
> Besides, add VCC supply capability on MediaTek UFS driver.
Applied to 5.2/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-04-04 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 15:32 [PATCH 0/2] scsi: dt-bindings: ufs: Remove "<name>-fixed-regulator" property and add VCC capability on MediaTek UFS driver Stanley Chu
[not found] ` <1553873568-9177-1-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-29 15:32 ` [PATCH 1/2] scsi: dt-bindings: ufs: Remove custom property "<name>-fixed-regulator" Stanley Chu
2019-03-29 15:32 ` [PATCH 2/2] scsi: dt-bindings: ufs: Add VCC capability on MediaTek UFS driver Stanley Chu
2019-04-04 3:26 ` 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=yq1imvutpqn.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=chun-hung.wu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pedrom.sousa@synopsys.com \
--cc=peter.wang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sayalil@codeaurora.org \
--cc=stanley.chu@mediatek.com \
--cc=subhashj@codeaurora.org \
--cc=vivek.gautam@codeaurora.org \
/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).