devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: hgkr.klein@gmail.com, linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5.1 2/2] ARM: dts: meson6: use stable UART bindings
Date: Tue, 08 Aug 2017 14:49:47 -0700	[thread overview]
Message-ID: <7hwp6dn30k.fsf@baylibre.com> (raw)
In-Reply-To: <1498056132-18508-3-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Wed, 21 Jun 2017 16:42:12 +0200")

Neil Armstrong <narmstrong@baylibre.com> writes:

> The UART bindings needs specifying a SoC family, use the meson6 family
> for the UART nodes like the other nodes.
> Switch to the stable UART bindings for meson6 by adding a XTAL node and
> using the proper compatible strings.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>

Applied to v4.14/dt,

Thanks,

Kevin

      reply	other threads:[~2017-08-08 21:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 14:42 [PATCH v5.1 0/2] tty/serial: meson_uart: add support for core clock handling Neil Armstrong
2017-06-21 14:42 ` [PATCH v5.1 1/2] ARM64: dts: meson-gx: use stable UART bindings with correct gate clock Neil Armstrong
     [not found]   ` <1498056132-18508-2-git-send-email-narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-08-08 21:49     ` Kevin Hilman
2017-12-03 14:15   ` Andreas Färber
     [not found]     ` <4e0d1db1-6382-a4b7-d112-3e45e0c1af2d-l3A5Bk7waGM@public.gmane.org>
2017-12-04  0:16       ` Andreas Färber
     [not found]         ` <61a59a32-a812-cc88-79f9-02c13f1901d7-l3A5Bk7waGM@public.gmane.org>
2017-12-04  8:52           ` Neil Armstrong
2017-06-21 14:42 ` [PATCH v5.1 2/2] ARM: dts: meson6: use stable UART bindings Neil Armstrong
2017-08-08 21:49   ` Kevin Hilman [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=7hwp6dn30k.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hgkr.klein@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    /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).