From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: "Paweł Jarosz" <paweljarosz3691-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>
Subject: Re: [RESEND] ARM: dts: rockchip: fix TSADC reset node for rk3066a
Date: Mon, 14 Nov 2016 00:11:56 +0100 [thread overview]
Message-ID: <1489175.liRG3HopZd@phil> (raw)
In-Reply-To: <CAFYR25XPx4QEu4bVyL2s4=Eqz+7w_Xjw8ZYOYzYsmz3z+rq84A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Paweł,
Am Sonntag, 13. November 2016, 17:02:39 CET schrieb Paweł Jarosz:
> This patch fixes incorectly assigned rk3066a TSADC node
>
> Signed-off-by: Paweł Jarosz <paweljarosz3691@gmail.com>
both patches from today look good, but your mailer seems to have scrambled the
patches when sending. Instead of tabs I see a lot of spaces for example, which
of course results in the patches not applying.
Heiko
> ---
> arch/arm/boot/dts/rk3066a.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/rk3066a.dtsi b/arch/arm/boot/dts/rk3066a.dtsi
> index fc8dcc7..ac46109 100644
> --- a/arch/arm/boot/dts/rk3066a.dtsi
> +++ b/arch/arm/boot/dts/rk3066a.dtsi
> @@ -205,7 +205,7 @@
> clock-names = "saradc", "apb_pclk";
> interrupts = <GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>;
> #io-channel-cells = <1>;
> - resets = <&cru SRST_SARADC>;
> + resets = <&cru SRST_TSADC>;
> reset-names = "saradc-apb";
> status = "disabled";
> };
> --
> 2.7.4
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2016-11-13 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 16:02 [RESEND] ARM: dts: rockchip: fix TSADC reset node for rk3066a Paweł Jarosz
[not found] ` <CAFYR25XPx4QEu4bVyL2s4=Eqz+7w_Xjw8ZYOYzYsmz3z+rq84A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-13 23:11 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-14 6:54 Paweł Jarosz
2016-11-14 9:32 ` Heiko Stuebner
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=1489175.liRG3HopZd@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=paweljarosz3691-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.