public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: soc@lists.linux.dev, Magnus Damm <magnus.damm@gmail.com>,
	 linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [GIT PULL 3/4] Renesas DT binding updates for v7.1
Date: Sat, 14 Mar 2026 12:09:40 +0100	[thread overview]
Message-ID: <20260314-quick-gray-saluki-0f96ff@quoll> (raw)
In-Reply-To: <cover.1773399673.git.geert+renesas@glider.be>

On Fri, Mar 13, 2026 at 12:12:59PM +0100, Geert Uytterhoeven wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> 
>   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-dt-bindings-for-v7.1-tag1
> 
> for you to fetch changes up to 3ac4e6b92fc200e047d13aae06224b2a72539b9e:
> 
>   dt-bindings: soc: renesas: renesas,rzg2l-sysc: Document RZ/G3L SoC (2026-03-06 13:38:54 +0100)
> 
> ----------------------------------------------------------------
> Renesas DT binding updates for v7.1
> 
>   - Document RZ/G3L SoC variants, the RZ/G3L SYSC block, and RZ/G3L
>     SMARC SoM and Carrier-II EVK boards.
> 
> ----------------------------------------------------------------
> Biju Das (2):
>       dt-bindings: soc: renesas: Document RZ/G3L SoC variants, SMARC SoM and Carrier-II EVK

This is DTS branch patch.

>       dt-bindings: soc: renesas: renesas,rzg2l-sysc: Document RZ/G3L SoC

This is drivers. Splitting it into additional branch is not making it
easier. I don't know where is this supposed to be merged. I will take it
to drivers, but in the future, please do not put DTS bindings into
driver bindings.

See also submitting patches in DT dir.

Best regards,
Krzysztof



  reply	other threads:[~2026-03-14 11:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 11:12 [GIT PULL 0/4] Renesas SoC updates for v7.1 Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 1/4] Renesas ARM defconfig " Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 2/4] Renesas driver " Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 3/4] Renesas DT binding " Geert Uytterhoeven
2026-03-14 11:09   ` Krzysztof Kozlowski [this message]
2026-03-16  8:51     ` Geert Uytterhoeven
2026-03-17  9:29       ` Krzysztof Kozlowski
2026-03-17  9:53         ` Krzysztof Kozlowski
2026-03-18 12:58           ` Arnd Bergmann
2026-03-13 11:13 ` [GIT PULL 4/4] Renesas DTS " Geert Uytterhoeven
2026-03-14 11:13   ` Krzysztof Kozlowski
2026-03-16  8:15     ` Geert Uytterhoeven
2026-03-14 11:23   ` Krzysztof Kozlowski
2026-03-16  8:18     ` Geert Uytterhoeven
2026-03-16  8:22       ` Krzysztof Kozlowski
2026-03-16  8:25         ` Geert Uytterhoeven
2026-03-17  8:32 ` [GIT PULL 0/4] Renesas SoC " Krzysztof Kozlowski
2026-03-17  8:46   ` Geert Uytterhoeven
2026-03-17  9:11     ` Krzysztof Kozlowski
2026-03-18 12:56       ` Arnd Bergmann
2026-03-18 13:12         ` Arnd Bergmann

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=20260314-quick-gray-saluki-0f96ff@quoll \
    --to=krzk@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=soc@lists.linux.dev \
    /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