linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: embed3d@gmail.com (Philipp Rossak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Fix broken bananapi m2 devicetree/regulators
Date: Thu, 15 Feb 2018 12:19:17 +0100	[thread overview]
Message-ID: <89d2da32-82c5-84d9-507e-aa17d782d766@gmail.com> (raw)
In-Reply-To: <20180215090838.fnenymzrejs6vhcf@flea.home>



On 15.02.2018 10:08, Maxime Ripard wrote:
> On Wed, Feb 14, 2018 at 03:10:23PM +0100, Philipp Rossak wrote:
>> This patchseries fixes the bananapi m1 devicetree, to be able to boot again.
>> The first two patches update/improve the devicetree and the last patch adds
>> all missing regulators.
>>
>> Regards,
>> Philipp
>>
>> Changes since v1:
>> 	* squashed commit 1 and 3
>> 	* fix wrong mmc regulator
>>
>> Philipp Rossak (2):
>>    arm: dts: sun6i: a31s: bpi-m2: improve pmic properties
>>    arm: dts: sun6i: a31s: fix: bpi-m2: add missing regulators
> 
> Applied both.
> 
> I had to make a couple of changes though, in the commit title arm
> should be uppercase, and the fix isn't needed.
> 
> I also added stable in Cc, since these patches have been there for
> quite some time.
> 
> Maxime
> 

Thanks!

Philipp

      reply	other threads:[~2018-02-15 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 14:10 [PATCH v2 0/2] Fix broken bananapi m2 devicetree/regulators Philipp Rossak
2018-02-14 14:10 ` [PATCH v2 1/2] arm: dts: sun6i: a31s: bpi-m2: improve pmic properties Philipp Rossak
2018-02-14 14:10 ` [PATCH v2 2/2] arm: dts: sun6i: a31s: fix: bpi-m2: add missing regulators Philipp Rossak
2018-02-15  9:08 ` [PATCH v2 0/2] Fix broken bananapi m2 devicetree/regulators Maxime Ripard
2018-02-15 11:19   ` Philipp Rossak [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=89d2da32-82c5-84d9-507e-aa17d782d766@gmail.com \
    --to=embed3d@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).