From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-gx: Add SPICC nodes
Date: Thu, 01 Jun 2017 11:59:53 +0200 [thread overview]
Message-ID: <1496311193.3552.3.camel@baylibre.com> (raw)
In-Reply-To: <m237bmsz61.fsf@baylibre.com>
On Tue, 2017-05-30 at 16:27 -0700, Kevin Hilman wrote:
> 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.
Now available : meson-clk-headers-for-4.13
>
> Kevin
>
prev parent reply other threads:[~2017-06-01 9:59 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
2017-06-01 9:59 ` Jerome Brunet [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=1496311193.3552.3.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--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).