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 4/4] Renesas DTS updates for v7.1
Date: Sat, 14 Mar 2026 12:13:19 +0100 [thread overview]
Message-ID: <20260314-arboreal-bold-vicugna-cdca27@quoll> (raw)
In-Reply-To: <cover.1773399675.git.geert+renesas@glider.be>
On Fri, Mar 13, 2026 at 12:13:00PM +0100, Geert Uytterhoeven wrote:
> The following changes since commit 85c2601e2c2feb60980c7ca23de28c49472f61f1:
>
> arm64: dts: renesas: r8a78000: Fix out-of-range SPI interrupt numbers (2026-03-06 13:15:21 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-dts-for-v7.1-tag1
>
> for you to fetch changes up to 0928a28daf017504e14920f4131bb99e3bc39dba:
>
> ARM: dts: renesas: armadillo800eva: Add wakeup-source to st1232 (2026-03-13 11:00:48 +0100)
Next analysis tells me:
Days in linux-next:
----------------------------------------
1 | ++ (2)
2 | ++++++ (6)
3 |
4 |
5 | ++++++++++++++++++++++ (22)
Please keep non-fix patches in the next for at least 3 next releases, so
you are sure any community tests/complains reached you. It is
unreasonable to expect that community will test your for-next patch
immediately the next day.
I merged other pulls but this one I will leave for few days more.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-14 11:13 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
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 [this message]
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-arboreal-bold-vicugna-cdca27@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