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 v5.17 (take two)
Date: Fri, 17 Dec 2021 12:07:11 +0100	[thread overview]
Message-ID: <cover.1639736716.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my second pull request for the inclusion of Renesas SoC updates
for v5.17.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v5.17

    - Enable support for the new R-Car S4-8 SoC in the arm64 defconfig.

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

    - Initial support for the R-Car S4-8 SoC on the Spider CPU and
      BreakOut boards,
    - MIPI DSI display support for the R-Car V3u SoC and the Falcon board
      stack,
    - Thermal and GPU support for the RZ/G2L SoC and the RZ/G2L SMARC EVK
      development board,
    - Miscellaneous fixes and improvements.

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

    - Core support for the R-Car S4-8 (R8A779F0) SoC, including System
      Controller (SYSC) and Reset (RST) support.

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

    - Document support for the R-Car S4-8 Spider CPU and BreakOut boards.

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

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 v5.17 (take two)
Date: Fri, 17 Dec 2021 12:07:11 +0100	[thread overview]
Message-ID: <cover.1639736716.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my second pull request for the inclusion of Renesas SoC updates
for v5.17.

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v5.17

    - Enable support for the new R-Car S4-8 SoC in the arm64 defconfig.

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

    - Initial support for the R-Car S4-8 SoC on the Spider CPU and
      BreakOut boards,
    - MIPI DSI display support for the R-Car V3u SoC and the Falcon board
      stack,
    - Thermal and GPU support for the RZ/G2L SoC and the RZ/G2L SMARC EVK
      development board,
    - Miscellaneous fixes and improvements.

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

    - Core support for the R-Car S4-8 (R8A779F0) SoC, including System
      Controller (SYSC) and Reset (RST) support.

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

    - Document support for the R-Car S4-8 Spider CPU and BreakOut boards.

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

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:[~2021-12-17 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 11:07 Geert Uytterhoeven [this message]
2021-12-17 11:07 ` [GIT PULL 0/4] Renesas SoC updates for v5.17 (take two) Geert Uytterhoeven
2021-12-17 11:07 ` [GIT PULL 1/4] Renesas ARM defconfig updates for v5.17 Geert Uytterhoeven
2021-12-17 11:07   ` Geert Uytterhoeven
2021-12-17 11:07 ` [GIT PULL 2/4] Renesas ARM DT updates for v5.17 (take two) Geert Uytterhoeven
2021-12-17 11:07   ` Geert Uytterhoeven
2021-12-17 11:07 ` [GIT PULL 3/4] Renesas driver " Geert Uytterhoeven
2021-12-17 11:07   ` Geert Uytterhoeven
2021-12-17 11:07 ` [GIT PULL 4/4] Renesas DT binding " Geert Uytterhoeven
2021-12-17 11:07   ` Geert Uytterhoeven
2021-12-17 15:20 ` [GIT PULL 0/4] Renesas SoC " 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.1639736716.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.