The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Yixun Lan <yixun.lan@amlogic.com>
Cc: <devicetree@vger.kernel.org>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Carlo Caione <carlo@caione.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] ARM64: dts: meson-axg: UART DT updates
Date: Tue, 30 Jan 2018 16:04:31 -0800	[thread overview]
Message-ID: <7hr2q6c2r4.fsf@baylibre.com> (raw)
In-Reply-To: <20180111023401.125658-1-yixun.lan@amlogic.com> (Yixun Lan's message of "Thu, 11 Jan 2018 10:33:56 +0800")

Yixun Lan <yixun.lan@amlogic.com> writes:

> HI Kevin
>  These are the UART DT updates for the Meson-AXG platform.
>
>  The patch 1 is a general fix.
> Other patches are about adding clock & pinctrl info, then using them.
> Last patch enable UART_A which connect to a BT module on the S400 board.

Applied to v4.16/dt64,

Thanks,

Kevin

  parent reply	other threads:[~2018-01-31  0:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11  2:33 [PATCH v3 0/5] ARM64: dts: meson-axg: UART DT updates Yixun Lan
2018-01-11  2:33 ` [PATCH v3 1/5] ARM64: dts: meson: uart: fix address space range Yixun Lan
2018-01-11  2:33 ` [PATCH v3 2/5] ARM64: dts: meson-axg: uart: drop legacy compatible name from EE UART Yixun Lan
2018-01-11  2:33 ` [PATCH v3 3/5] ARM64: dts: meson-axg: uart: Add the pinctrl info description Yixun Lan
2018-01-11  2:34 ` [PATCH v3 4/5] ARM64: dts: meson-axg: complete the pinctrl info for UART_AO_A Yixun Lan
2018-01-11  2:34 ` [PATCH v3 5/5] ARM64: dts: meson-axg: enable the UART_A controller Yixun Lan
2018-01-31  0:04 ` Kevin Hilman [this message]
2018-01-31  0:22   ` [PATCH v3 0/5] ARM64: dts: meson-axg: UART DT updates Kevin Hilman
2018-01-31  2:25     ` Yixun Lan
2018-02-01 22:36       ` 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=7hr2q6c2r4.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=narmstrong@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=yixun.lan@amlogic.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