linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>, linux-amlogic@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm64: dts: meson: add g12a x96 max board
Date: Mon, 21 Jan 2019 11:43:46 +0100	[thread overview]
Message-ID: <4d1ae3a6-874a-f032-a873-a715a67a3992@baylibre.com> (raw)
In-Reply-To: <20181219233519.35287-2-khilman@baylibre.com>

Hi Kevin,

On 20/12/2018 00:35, Kevin Hilman wrote:
> Add the G12a (S905X2) based X96 Max board[1].
> 
> There is no branding for the manufacturer anywhere on the product, so it
> took some digging to find the manufacturer.  But since there's nothing
> about the maker on the product I've left it out of the DT name because
> 1) nobody will know that name and 2) keeps the DT filename shorter.
> 
> [1] https://www.cnx-software.com/2018/09/25/x96-max-amlogic-s905x2-tv-box/
> 
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
>  .../boot/dts/amlogic/meson-g12a-x96-max.dts   | 28 +++++++++++++++++++

Just found out you forgot to update the Makefile !!

Neil

[snip]

> +
> +&uart_AO {
> +	status = "okay";
> +};
> 


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-01-21 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 23:35 [PATCH v2 1/2] dt-bindings: arm: amlogic: add amediatech x96-max bindings Kevin Hilman
2018-12-19 23:35 ` [PATCH v2 2/2] arm64: dts: meson: add g12a x96 max board Kevin Hilman
2019-01-21 10:43   ` Neil Armstrong [this message]
2019-01-31 16:48     ` Kevin Hilman
2018-12-21 22:12 ` [PATCH v2 1/2] dt-bindings: arm: amlogic: add amediatech x96-max bindings Chris Moore
2018-12-21 23:13   ` Kevin Hilman
2019-01-31 16:48   ` Kevin Hilman
2018-12-22 16:40 ` Martin Blumenstingl
2019-01-31 16:49   ` Kevin Hilman

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=4d1ae3a6-874a-f032-a873-a715a67a3992@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --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).