public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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: Mon, 16 Mar 2026 09:22:33 +0100	[thread overview]
Message-ID: <b5d2f9a6-8039-48fb-8d7e-ee7823c504e3@kernel.org> (raw)
In-Reply-To: <CAMuHMdWLOCvKfp4bULzm6N_3u1Mh831Z0EW++8473wvs29MRHQ@mail.gmail.com>

On 16/03/2026 09:18, Geert Uytterhoeven wrote:
> Hi Krzysztof,
> 
> On Sat, 14 Mar 2026 at 12:23, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>> On 13/03/2026 12:13, 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)
>>
>> Also nothing explains me what is this, IOW, why this is not RC1. Pull
>> request email has place at the beginning where you explain such things
>> and I can easily locate or understand the base.
> 
> Let's readd the part you cut, which is also present in the cover letter:
> 
>>> Note that this PR is based on "[GIT PULL] Renesas SoC fixes for v7.0".

Ah... no one reads cover letters :) so I expected that information here,
before the pull boilerplate. I guess this depends on scripting, so it's
fine. I will look for cover letters in the future.

Best regards,
Krzysztof


  reply	other threads:[~2026-03-16  8:22 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
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 [this message]
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=b5d2f9a6-8039-48fb-8d7e-ee7823c504e3@kernel.org \
    --to=krzk@kernel.org \
    --cc=geert@linux-m68k.org \
    --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