Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, 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/3] Renesas SoC updates for v6.4 (take two)
Date: Mon, 10 Apr 2023 09:55:25 +0200	[thread overview]
Message-ID: <cover.1681113111.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my second pull request for the inclusion of Renesas SoC updates
for v6.4.

It consists of 3 parts:

  [GIT PULL 1/3] Renesas ARM SoC updates for v6.4

    - Use of_cpu_node_to_id() to read CPU node 'reg'.

  [GIT PULL 2/3] Renesas driver updates for v6.4 (take two)

    - Add "renesas," file contents pattern to MAINTAINERS,
    - Fix a small leak on OOM.

  [GIT PULL 3/3] Renesas DTS updates for v6.4 (take two)

    - Add PWM support for the R-Car H1 and H2 SoCs,
    - Add slide switch and I2C support for the Marzen development board,
    - Add SCI (serial) and Camera support for the RZ/G2L SoC and the
      RZ/G2L SMARC EVK development board,
    - Add IOMMU support for the R-Car V4H SoC,
    - Miscellaneous fixes and improvements.

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:[~2023-04-10  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  7:55 Geert Uytterhoeven [this message]
2023-04-10  7:55 ` [GIT PULL 1/3] Renesas ARM SoC updates for v6.4 Geert Uytterhoeven
2023-04-10  7:55 ` [GIT PULL 2/3] Renesas driver updates for v6.4 (take two) Geert Uytterhoeven
2023-04-10  7:55 ` [GIT PULL 3/3] Renesas DTS " 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=cover.1681113111.git.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