All of lore.kernel.org
 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/4] Renesas SoC updates for v6.9
Date: Fri,  9 Feb 2024 17:54:49 +0100	[thread overview]
Message-ID: <cover.1707487826.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v6.9.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v6.9

    - Disable obsolete board staging support in the Renesas ARM and ARM V7
      multi-platform defconfigs,
    - Enable support for the Renesas R-Car V4M (R8A779H0) SoC in the ARM64
      defconfig.

  [GIT PULL 2/4] Renesas driver updates for v6.9

    - Initial support for the Renesas R-Car V4M (R8A779H0) SoC.

  [GIT PULL 3/4] Renesas DT binding updates for v6.9

    - Document support for the Renesas R-Car V4M (R8A779H0) SoC, and the
      White Hawk Single and Gray Hawk Single development boards.

  [GIT PULL 4/4] Renesas DTS updates for v6.9

    - Add GPIO keys and watchdog support for the RZ/G3S SMARC development
      board,
    - Add GNSS support for Renesas ULCB development boards equipped with
      the Shimafuji Kingfisher extension,
    - Add support for the standalone White Hawk CPU board,
    - Add support for the R-Car V4H ES2.0 (R8A779G2) SoC and the White
      Hawk Single development board,
    - Add initial support for the R-Car V4M (R8A779H0) SoC and the Gray
      Hawk Single development board,
    - Add camera support for the RZ/G2UL 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

WARNING: multiple messages have this Message-ID (diff)
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/4] Renesas SoC updates for v6.9
Date: Fri,  9 Feb 2024 17:54:49 +0100	[thread overview]
Message-ID: <cover.1707487826.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v6.9.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v6.9

    - Disable obsolete board staging support in the Renesas ARM and ARM V7
      multi-platform defconfigs,
    - Enable support for the Renesas R-Car V4M (R8A779H0) SoC in the ARM64
      defconfig.

  [GIT PULL 2/4] Renesas driver updates for v6.9

    - Initial support for the Renesas R-Car V4M (R8A779H0) SoC.

  [GIT PULL 3/4] Renesas DT binding updates for v6.9

    - Document support for the Renesas R-Car V4M (R8A779H0) SoC, and the
      White Hawk Single and Gray Hawk Single development boards.

  [GIT PULL 4/4] Renesas DTS updates for v6.9

    - Add GPIO keys and watchdog support for the RZ/G3S SMARC development
      board,
    - Add GNSS support for Renesas ULCB development boards equipped with
      the Shimafuji Kingfisher extension,
    - Add support for the standalone White Hawk CPU board,
    - Add support for the R-Car V4H ES2.0 (R8A779G2) SoC and the White
      Hawk Single development board,
    - Add initial support for the R-Car V4M (R8A779H0) SoC and the Gray
      Hawk Single development board,
    - Add camera support for the RZ/G2UL 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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2024-02-09 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 16:54 Geert Uytterhoeven [this message]
2024-02-09 16:54 ` [GIT PULL 0/4] Renesas SoC updates for v6.9 Geert Uytterhoeven
2024-02-09 16:54 ` [GIT PULL 1/4] Renesas ARM defconfig " Geert Uytterhoeven
2024-02-09 16:54   ` Geert Uytterhoeven
2024-02-09 16:54 ` [GIT PULL 2/4] Renesas driver " Geert Uytterhoeven
2024-02-09 16:54   ` Geert Uytterhoeven
2024-02-09 16:54 ` [GIT PULL 3/4] Renesas DT binding " Geert Uytterhoeven
2024-02-09 16:54   ` Geert Uytterhoeven
2024-02-09 16:54 ` [GIT PULL 4/4] Renesas DTS " Geert Uytterhoeven
2024-02-09 16:54   ` Geert Uytterhoeven
2024-02-20 21:12 ` [GIT PULL 0/4] Renesas SoC " patchwork-bot+linux-soc
2024-02-29 17:02 ` patchwork-bot+linux-soc

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.1707487826.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.