[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDyKFo=UdnVhFU7k+K1=N0e-1sniC+WZjZ4dZKSF8mXhM43Uw@mail.gmail.com>
Date: Fri, 1 Sep 2017 15:18:03 +0200
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Ravikumar Kattekola <rk@...com>, Sekhar Nori <nsekhar@...com>,
Adrian Hunter <adrian.hunter@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Tony Lindgren <tony@...mide.com>,
Liam Girdwood <lgirdwood@...il.com>,
Russell King <linux@...linux.org.uk>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Applied "regulator: pbias: Select voltage table based on
max-voltage" to the regulator tree
On 31 August 2017 at 15:50, Mark Brown <broonie@...nel.org> wrote:
> On Thu, Aug 31, 2017 at 05:37:34PM +0530, Kishon Vijay Abraham I wrote:
>
>> This patch should be merged along with the 1st patch of the series "mmc: host:
>> omap_hsmmc: Remove setting PBIAS voltage". Or else it'll break MMC with
>> omap_hsmmc driver.
>
> I can sign a tag if it's needed for a cross tree merge.
Easier if you could drop it and instead just provide an ack.
Unless you believes there may conflict in your regulator tree?
Kind regards
Uffe
Powered by blists - more mailing lists