From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM64: dts: meson-gx: Add SPICC nodes
Date: Tue, 30 May 2017 16:27:50 -0700 [thread overview]
Message-ID: <m237bmsz61.fsf@baylibre.com> (raw)
In-Reply-To: <m27f0yt2cv.fsf@baylibre.com> (Kevin Hilman's message of "Tue, 30 May 2017 15:18:56 -0700")
Kevin Hilman <khilman@baylibre.com> writes:
> Neil Armstrong <narmstrong@baylibre.com> writes:
>
>> Add nodes for the SPICC controller on GX common dtsi, GXBB and
>> GXL dtsi files.
>>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>
> Applied to v4.13/dt64,
Oops, this one will have to wait until we have an immutable branch in
the clk tree.
Kevin
next prev parent reply other threads:[~2017-05-30 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 8:09 [PATCH] ARM64: dts: meson-gx: Add SPICC nodes Neil Armstrong
2017-05-30 22:18 ` Kevin Hilman
2017-05-30 23:27 ` Kevin Hilman [this message]
2017-06-01 9:59 ` Jerome Brunet
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=m237bmsz61.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--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).