From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: sun8i: Orange Pi Plus dts is for the Plus and Plus 2
Date: Mon, 5 Sep 2016 13:35:44 +0200 [thread overview]
Message-ID: <20160905113544.GD6322@lukather> (raw)
In-Reply-To: <20160903110518.8267-1-hdegoede@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 524 bytes --]
On Sat, Sep 03, 2016 at 01:05:17PM +0200, Hans de Goede wrote:
> Update the sun8i-h3-orangepi-plus.dts model string to reflect that it
> is valid for both the Orange Pi Plus and the Orange Pi Plus 2.
>
> This is also meant to help users realize that it is not valid for
> the new Orange Pi Plus 2E, which will get its own dts.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2016-09-05 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 11:05 [PATCH 1/2] ARM: dts: sun8i: Orange Pi Plus dts is for the Plus and Plus 2 Hans de Goede
[not found] ` <20160903110518.8267-1-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-03 11:05 ` [PATCH 2/2] ARM: dts: sun8i: Add dts file for the Orange Pi Plus2E SBC Hans de Goede
[not found] ` <20160903110518.8267-2-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-05 11:36 ` Maxime Ripard
2016-09-05 11:35 ` Maxime Ripard [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=20160905113544.GD6322@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).