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/2] Renesas ARM SoC updates for v5.12
Date: Fri, 15 Jan 2021 10:46:08 +0100	[thread overview]
Message-ID: <20210115094610.2334058-1-geert+renesas@glider.be> (raw)

	Hi arm-soc folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v5.12.

It consists of 2 parts:

  [GIT PULL 1/2] Renesas ARM DT updates for v5.12

    - Timer (CMT/TMU) support for R-Car Gen3 SoCs,
    - Watchdog (RWDT), pincontrol (PFC), GPIO, and DMA (SYS-DMAC) support
      for the R-Car V3U SoC,
    - USB2 clock selector and SPI Multi I/O Bus Controller (RPC-IF)
      support for RZ/G2 SoCs,
    - Support for the Beacon EmbeddedWorks RZ/G2H and RZ/G2N kits,
    - Various fixes and improvements.

  [GIT PULL 2/2] Renesas DT binding updates for v5.12

    - Document suport for the Beacon EmbeddedWorks RZ/G2N and RZ/H kits.

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:[~2021-01-15  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  9:46 Geert Uytterhoeven [this message]
2021-01-15  9:46 ` [GIT PULL 1/2] Renesas ARM DT updates for v5.12 Geert Uytterhoeven
2021-01-15  9:46 ` [GIT PULL 2/2] 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=20210115094610.2334058-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).