From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: jorik@kippendief.biz
Cc: wens@csie.org, robh+dt@kernel.org, mark.rutland@arm.com,
linux@armlinux.org.uk, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
arm@kernel.org
Subject: Re: [PATCH] dts: sun8i-h3: correct UART3 pin definitions
Date: Tue, 6 Dec 2016 15:05:38 +0100 [thread overview]
Message-ID: <20161206140538.ag7nofyca2n5ror2@lukather> (raw)
In-Reply-To: <20161204122948.11921-1-jorik@kippendief.biz>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Hi Jorik,
On Sun, Dec 04, 2016 at 01:29:48PM +0100, jorik@kippendief.biz wrote:
> From: Jorik Jonker <jorik@kippendief.biz>
>
> In a previous commit, I made a copy/paste error in the pinmux
> definitions of UART3: PG{13,14} instead of PA{13,14}. This commit takes
> care of that. I have tested this commit on Orange Pi PC and Orange Pi
> Plus, and it works for these boards.
>
> Fixes: e3d11d3c45c5 ("dts: sun8i-h3: add pinmux definitions for
> UART2-3")
>
> Signed-off-by: Jorik Jonker <jorik@kippendief.biz>
Thanks!
This looks like a late fix for the current release which comes to an
end. Can you resend it with arm@kernel.org as a recipient, so that the
ARM SoC maintainers can apply it directly?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-12-06 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 12:29 [PATCH] dts: sun8i-h3: correct UART3 pin definitions jorik
2016-12-06 14:05 ` Maxime Ripard [this message]
2016-12-06 14:27 jorik
2016-12-06 14:31 ` Maxime Ripard
2016-12-07 20:40 ` Olof Johansson
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=20161206140538.ag7nofyca2n5ror2@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jorik@kippendief.biz \
--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=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;
as well as URLs for NNTP newsgroup(s).