From: Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
To: Geert Uytterhoeven
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
Cc: Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/4] ARM: shmobile: Document and identify RZ/G1H and RZ/G1N
Date: Mon, 13 Mar 2017 10:26:37 +0100 [thread overview]
Message-ID: <20170313092636.GD19296@verge.net.au> (raw)
In-Reply-To: <1489153710-8159-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
On Fri, Mar 10, 2017 at 02:48:26PM +0100, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> Now the part numbers of the Renesas RZ/G1H and RZ/G1N are publicly
> available, this patch series documents the DT bindings for these SoCs,
> and adds support for identifying them.
>
> Thanks!
Thanks, applied.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-03-13 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 13:48 [PATCH 0/4] ARM: shmobile: Document and identify RZ/G1H and RZ/G1N Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 1/4] ARM: shmobile: Document RZ/G1H SoC DT binding Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 2/4] ARM: shmobile: Document RZ/G1N " Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 3/4] soc: renesas: Identify RZ/G1H Geert Uytterhoeven
2017-03-10 13:48 ` [PATCH 4/4] soc: renesas: Identify RZ/G1N Geert Uytterhoeven
[not found] ` <1489153710-8159-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-03-13 9:26 ` Simon Horman [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=20170313092636.GD19296@verge.net.au \
--to=horms-/r6kz+ddxgppr4jqbcensq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).