On 09/22/2012 09:56 AM, Mark Brown wrote:
> On Thu, Sep 20, 2012 at 04:04:57PM -0600, Stephen Warren wrote:
>
>> Mark, if this gets into 3.7, I can fix up all the Tegra .dts files during
>> 3.8.
>
> I don't know which branch you generated this against but it doesn't
> apply to any of the
On Thu, Sep 20, 2012 at 04:04:57PM -0600, Stephen Warren wrote:
> Mark, if this gets into 3.7, I can fix up all the Tegra .dts files during 3.8.
I don't know which branch you generated this against but it doesn't
apply to any of the obvious branches in my regulator tree. There's a
modify/delete
On Thu, Sep 20, 2012 at 04:04:57PM -0600, Stephen Warren wrote:
Mark, if this gets into 3.7, I can fix up all the Tegra .dts files during 3.8.
I don't know which branch you generated this against but it doesn't
apply to any of the obvious branches in my regulator tree. There's a
modify/delete
On 09/22/2012 09:56 AM, Mark Brown wrote:
On Thu, Sep 20, 2012 at 04:04:57PM -0600, Stephen Warren wrote:
Mark, if this gets into 3.7, I can fix up all the Tegra .dts files during
3.8.
I don't know which branch you generated this against but it doesn't
apply to any of the obvious
From: Stephen Warren
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init data should be named
From: Stephen Warren swar...@nvidia.com
When the bindings for the TPS6586x regulator were being proposed, I
asserted that DT node naming rules for bus child nodes should also be
applied to nodes inside the TPS6586x regulator node itself. In other
words, that each node providing regulator init
6 matches
Mail list logo
