From: Kishon Vijay Abraham I <kishon@ti.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] omap_hsmmc: use mmc_regulator_get_supply() to get regulators
Date: Fri, 9 Jun 2017 13:21:17 +0530 [thread overview]
Message-ID: <19f289a5-cc1d-a14a-130a-ae45710d969e@ti.com> (raw)
In-Reply-To: <CAPDyKFrMnZ0EGjdm4J0mTuaq+dp8eTEr3W-pOCowuwNEV2zwYw@mail.gmail.com>
Hi Uffe,
On Thursday 08 June 2017 12:45 PM, Ulf Hansson wrote:
> On 7 June 2017 at 10:36, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>> This series deprecates "vmmc_aux" supply property and uses the generic
>> "vqmmc" property.
>>
>> Not sure how exactly to handle omap3-overo-base.dtsi which already has
>> both vqmmc-supply and vmmc_aux-supply without breaking old dt
>> compatibility. (vqmmc-supply seems to have been added there by mistake
>> from 3.15).
>>
>> In the dt series that will follow, will replace all vmmc_aux-supply
>> with vqmmc-supply (In omap3-overo-base.dtsi remove the existing
>> vqmmc-supply and then replace vmmc_aux-supply with vqmmc-supply).
>>
>> Kishon Vijay Abraham I (3):
>> mmc: host: omap_hsmmc: Do not initialize MMC regulators to NULL on
>> error
>> mmc: host: omap_hsmmc: use mmc_regulator_get_supply() to get
>> regulators
>> Documentation: dt-bindings: Document deprecation of "vmmc_aux" and
>> using "vqmmc"
>>
>> .../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 2 +-
>> drivers/mmc/host/omap_hsmmc.c | 55 +++++++++-------------
>> 2 files changed, 24 insertions(+), 33 deletions(-)
>>
>> --
>> 2.11.0
>>
>
> Besides the minor comment for patch2 this looks good to me.
>
> In case there are no other comments, and that you agree with my
> suggested change, you don't need to re-spin.
Your suggested change looks good.
Thanks
Kishon
next prev parent reply other threads:[~2017-06-09 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 8:36 [PATCH 0/3] omap_hsmmc: use mmc_regulator_get_supply() to get regulators Kishon Vijay Abraham I
2017-06-07 8:36 ` [PATCH 1/3] mmc: host: omap_hsmmc: Do not initialize MMC regulators to NULL on error Kishon Vijay Abraham I
2017-06-07 8:36 ` [PATCH 2/3] mmc: host: omap_hsmmc: use mmc_regulator_get_supply() to get regulators Kishon Vijay Abraham I
2017-06-08 7:12 ` Ulf Hansson
2017-06-07 8:36 ` [PATCH 3/3] Documentation: dt-bindings: Document deprecation of "vmmc_aux" and using "vqmmc" Kishon Vijay Abraham I
2017-06-09 13:53 ` Rob Herring
2017-06-08 7:15 ` [PATCH 0/3] omap_hsmmc: use mmc_regulator_get_supply() to get regulators Ulf Hansson
2017-06-09 7:51 ` Kishon Vijay Abraham I [this message]
[not found] ` <19f289a5-cc1d-a14a-130a-ae45710d969e-l0cyMroinI0@public.gmane.org>
2017-06-12 7:59 ` Ulf Hansson
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=19f289a5-cc1d-a14a-130a-ae45710d969e@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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