From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, arm-soc <soc@kernel.org>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PULL 0/5] Renesas SoC updates for v5.4 (take two)
Date: Fri, 23 Aug 2019 14:36:38 +0200 [thread overview]
Message-ID: <20190823123643.18799-1-geert+renesas@glider.be> (raw)
Hi arm-soc folks,
This is my second pull request for the inclusion of Renesas SoC updates
for v5.4.
It consists of 5 parts:
[PULL 1/5] Renesas ARM DT updates for v5.4
- Fix HSCIF PM Domain on R-Car H1,
- PMU support for RZ/G1C.
[PULL 2/5] Renesas ARM SoC updates for v5.4
- Low-level debugging support for RZ/A2M.
[PULL 3/5] Renesas ARM64 DT updates for v5.4 (take two)
- Sort nodes in various SoC and board DTSes,
- HDMI sound for HiHope RZ/G2M and R-Car M3-N Salvator-X(S) boards,
- Limit EtherAVB to 100Mbps on the Ebisu and Draak boards,
- Small fixes and improvements.
[PULL 4/5] Renesas driver updates for v5.4 (take two)
- Improve "always-on" PM Domain handling on SH/R-Mobile SoCs,
- Automatic errata selection for Cortex-A7/A9,
- Small fixes and improvements.
[PULL 5/5] Renesas DT binding updates for v5.4 (take two)
- Renesas DT binding doc filename cleanups,
- R-Car Gen3 and RZ/G1 updates for the R-Car CAN and CANFD DT
bindings.
For now I more or less followed Simon's way of structuring the branches,
but I'm open for change. Hence if you have any comments, or suggestions
for improving the workflow, please let me know.
Thanks for pulling, and for your comments!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2019-08-23 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:36 Geert Uytterhoeven [this message]
2019-08-23 12:36 ` [PULL 1/5] Renesas ARM DT updates for v5.4 Geert Uytterhoeven
2019-09-03 13:36 ` Arnd Bergmann
2019-08-23 12:36 ` [PULL 2/5] Renesas ARM SoC " Geert Uytterhoeven
2019-09-03 21:14 ` Arnd Bergmann
2019-09-04 7:15 ` Geert Uytterhoeven
2019-08-23 12:36 ` [PULL 3/5] Renesas ARM64 DT updates for v5.4 (take two) Geert Uytterhoeven
2019-09-03 13:53 ` Arnd Bergmann
2019-08-23 12:36 ` [PULL 4/5] Renesas driver " Geert Uytterhoeven
2019-09-03 20:16 ` Arnd Bergmann
2019-08-23 12:36 ` [PULL 5/5] Renesas DT binding " Geert Uytterhoeven
2019-09-03 13:55 ` Arnd Bergmann
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=20190823123643.18799-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arm@kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=soc@kernel.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).