linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, arm-soc <soc@kernel.org>
Cc: 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: [GIT PULL 0/5] Renesas SoC updates for v5.8 (take two)
Date: Fri, 15 May 2020 12:05:42 +0200	[thread overview]
Message-ID: <20200515100547.14671-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.8.

It consists of 5 parts:

  [GIT PULL 1/5] Renesas ARM defconfig updates for v5.8 (take two)

    - Enable support for the new RZ/G1H SoC in the shmobile and multi_v7
      defconfigs.

  [GIT PULL 2/5] Renesas ARM DT updates for v5.8 (take two)

    - Initial support for the Renesas RZ/G1H SoC on the iWave RainboW
      Qseven SOM (G21M) and board (G21D),
    - Support for the AISTARVISION MIPI Adapter V2.1 camera board on the
      Silicon Linux EK874 RZ/G2E evaluation kit.

  [GIT PULL 3/5] Renesas ARM SoC updates for v5.8 (take two)

    - Add debug-ll support for RZ/G1H.

  [GIT PULL 4/5] Renesas driver updates for v5.8 (take two)

    - Add the main config option for the RZ/G1H SoC.

  [GIT PULL 5/5] Renesas DT binding updates for v5.8 (take two)

    - Document support for the RZ/G1H-based iWave RainboW Qseven SOM
      (G21M) and board (G21D).

Note that the new Renesas RZ/G1H DT Binding Definitions are shared by
driver and DT source files, and thus included in multiple pull requests:
  - "[GIT PULL 2/5] Renesas ARM DT updates for v5.8 (take two)",
  - "[GIT PULL 4/5] Renesas driver updates for v5.8" (previous PR),
  - "[GIT PULL] clk: renesas: Updates for v5.8" (for clk).

Thanks for pulling!

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

             reply	other threads:[~2020-05-15 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 10:05 Geert Uytterhoeven [this message]
2020-05-15 10:05 ` [GIT PULL 1/5] Renesas ARM defconfig updates for v5.8 (take two) Geert Uytterhoeven
2020-05-15 10:05 ` [GIT PULL 2/5] Renesas ARM DT " Geert Uytterhoeven
2020-05-15 10:05 ` [GIT PULL 3/5] Renesas ARM SoC " Geert Uytterhoeven
2020-05-15 10:05 ` [GIT PULL 4/5] Renesas driver " Geert Uytterhoeven
2020-05-15 10:05 ` [GIT PULL 5/5] Renesas DT binding " Geert Uytterhoeven

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=20200515100547.14671-1-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=arm@kernel.org \
    --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).