mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Suloev <ssuloev@orpaltech.com>
To: Philipp Rossak <embed3d@gmail.com>,
	robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	maxime.ripard@free-electrons.com, wens@csie.org
Cc: devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators
Date: Sat, 10 Feb 2018 16:56:43 +0300	[thread overview]
Message-ID: <160b60e2-6e50-0d63-e6ac-b67e10317e12@orpaltech.com> (raw)
In-Reply-To: <20180209175236.21215-1-embed3d@gmail.com>

On 02/09/2018 08:52 PM, 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
>
> Philipp Rossak (3):
>    arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes
>    arm: dts: sun6i: a31s: bpi-m2: improve pmic properties
>    arm: dts: sun6i: a31s: fix: bpi-m2: add missing regulators
>
>   arch/arm/boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts | 70 +++++++++++++++++++++++-
>   1 file changed, 67 insertions(+), 3 deletions(-)
>
patches are not working

Thanks

  parent reply	other threads:[~2018-02-10 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 17:52 Philipp Rossak
2018-02-09 17:52 ` [PATCH 1/3] arm: dts: sun6i: a31s: bpi-m2: update mmc supply nodes Philipp Rossak
2018-02-11 22:15   ` Philipp Rossak
2018-02-09 17:52 ` [PATCH 2/3] arm: dts: sun6i: a31s: bpi-m2: improve pmic properties Philipp Rossak
2018-02-09 17:52 ` [PATCH 3/3] arm: dts: sun6i: a31s: fix: bpi-m2: add missing regulators Philipp Rossak
2018-02-10 13:56 ` Sergey Suloev [this message]
2018-02-10 21:01   ` [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators Philipp Rossak
2018-02-10 21:08     ` Sergey Suloev
2018-02-10 22:07       ` Philipp Rossak
2018-02-11  7:29         ` Sergey Suloev
2018-02-11  7:55         ` Sergey Suloev
2018-02-11 11:30           ` Philipp Rossak
2018-02-11 11:36             ` Sergey Suloev
2018-02-11 11:44             ` Sergey Suloev

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=160b60e2-6e50-0d63-e6ac-b67e10317e12@orpaltech.com \
    --to=ssuloev@orpaltech.com \
    --cc=devicetree@vger.kernel.org \
    --cc=embed3d@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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
Powered by JetHome