From: Krzysztof Kozlowski <krzk@kernel.org>
To: Paul Barker <paul.barker.ct@bp.renesas.com>,
Thierry Bultel <thierry.bultel.yh@bp.renesas.com>
Cc: thierry.bultel@linatsea.fr, linux-renesas-soc@vger.kernel.org,
geert@linux-m68k.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 02/13] dt-bindings: clock: Add cpg for the Renesas RZ/T2H SoC
Date: Wed, 26 Mar 2025 11:32:02 +0100 [thread overview]
Message-ID: <69bb8311-c0f7-4940-8c69-8b6de4f7c30e@kernel.org> (raw)
In-Reply-To: <d2d09918-5555-47a7-8b82-f88e9ff022d7@bp.renesas.com>
On 26/03/2025 11:28, Paul Barker wrote:
> On 26/03/2025 07:49, Krzysztof Kozlowski wrote:
>> On Tue, Mar 25, 2025 at 05:08:50PM +0100, Thierry Bultel wrote:
>>> Document RZ/T2H (a.k.a r9a09g077) cpg-mssr (Clock Pulse Generator) binding.
>>>
>>> Signed-off-by: Thierry Bultel <thierry.bultel.yh@bp.renesas.com>
>>> ---
>>> Changes v4->v5:
>>> - Set reg minItems and maxItems defaults at top level
>>> Changes v3->v4:
>>> - Handle maxItems and clocks names properly in schema.
>>
>>
>> Can you start using b4 or send patchsets in standard way? No links to
>> previous versions in changelog and b4 diff does not work:
>>
>> b4 diff '20250325160904.2688858-1-thierry.bultel.yh@bp.renesas.com'
>> Grabbing thread from lore.kernel.org/all/20250325160904.2688858-1-thierry.bultel.yh@bp.renesas.com/t.mbox.gz
>> Checking for older revisions
>> Grabbing search results from lore.kernel.org
>> Added from v4: 14 patches
>> ---
>> Analyzing 140 messages in the thread
>> Preparing fake-am for v4: dt-bindings: soc: Add Renesas RZ/T2H (R9A09G077) SoC
>> ERROR: Could not fake-am version v4
>> ---
>> Could not create fake-am range for lower series v4
>
> Hi Krzysztof,
>
> The above b4 command works for me. Which b4 version are you using and
> which base tree do you have checked out?
>
> FYI, this series now applies cleanly on top of tty-next as Geert's
> patch [1] has been integrated.
>
> [1]: https://lore.kernel.org/linux-renesas-soc/11c2eab45d48211e75d8b8202cce60400880fe55.1741114989.git.geert+renesas@glider.be/T/#u
Latest b4 and latest next (next-20250321). I tried next-20250317 as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-26 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250325160904.2688858-1-thierry.bultel.yh@bp.renesas.com>
2025-03-25 16:08 ` [PATCH v5 01/13] dt-bindings: soc: Add Renesas RZ/T2H (R9A09G077) SoC Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 02/13] dt-bindings: clock: Add cpg for the Renesas RZ/T2H SoC Thierry Bultel
2025-03-26 7:49 ` Krzysztof Kozlowski
2025-03-26 10:28 ` Paul Barker
2025-03-26 10:32 ` Krzysztof Kozlowski [this message]
2025-03-31 10:17 ` Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 03/13] dt-bindings: serial: Add compatible for Renesas RZ/T2H SoC in sci Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 04/13] soc: renesas: Add RZ/T2H (R9A09G077) config option Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 05/13] clk: renesas: Pass sub struct of cpg_mssr_priv to cpg_clk_register Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 06/13] clk: renesas: Add support for R9A09G077 SoC Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 07/13] serial: sh-sci: Fix a comment about SCIFA Thierry Bultel
2025-03-26 9:49 ` Geert Uytterhoeven
2025-03-25 16:08 ` [PATCH v5 08/13] serial: sh-sci: Introduced function pointers Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 09/13] serial: sh-sci: Introduced sci_of_data Thierry Bultel
2025-03-25 16:08 ` [PATCH v5 10/13] serial: sh-sci: Add support for RZ/T2H SCI Thierry Bultel
2025-03-25 16:23 ` Wolfram Sang
2025-03-25 16:08 ` [PATCH v5 11/13] arm64: dts: renesas: Add initial support for renesas RZ/T2H SoC Thierry Bultel
2025-03-25 16:09 ` [PATCH v5 12/13] arm64: dts: renesas: Add initial support for renesas RZ/T2H eval board Thierry Bultel
2025-03-25 16:09 ` [PATCH v5 13/13] arm64: defconfig: Enable Renesas RZ/T2H serial SCI Thierry Bultel
2025-03-25 16:24 ` Wolfram Sang
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=69bb8311-c0f7-4940-8c69-8b6de4f7c30e@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=paul.barker.ct@bp.renesas.com \
--cc=thierry.bultel.yh@bp.renesas.com \
--cc=thierry.bultel@linatsea.fr \
/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
all inboxes | Powered by JetHome®