public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Neil Armstrong" <neil.armstrong@linaro.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: soc@kernel.org, arm <arm@kernel.org>,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] amlogic ARM64 DT updates for v7.1
Date: Mon, 20 Apr 2026 21:41:04 +0200	[thread overview]
Message-ID: <d95cfc82-327f-4bed-95ae-88a9182eedba@app.fastmail.com> (raw)
In-Reply-To: <5d9c1c31-5e89-4699-b910-f5ca2c36260f@linaro.org>

On Mon, Apr 20, 2026, at 19:31, Neil Armstrong wrote:
> On 4/20/26 17:25, Arnd Bergmann wrote:
>> On Mon, Apr 13, 2026, at 09:30, Krzysztof Kozlowski wrote:
>> - I see that only a few of the patches in the branch got applied
>>    during the fineal days before the merge window, while the rest
>>    had been part of next-20260330 or earlier. Aside from just
>>    sending the bulk of the contents earlier, I think the best
>>    solution on Neil's side would have been to send two separate
>>    pull requests, for the earlier and the later contents
>>    respectively, even if sending them on the same day
>
> I never did a split because I don't have enought changes to justify
> 2 PRs and I had some contributors & other maintainers activity late
> in the cycle.
> Anyway I'll make sure to send the PRs earlier.

Ok, thanks! Note that I rarely complain about a follow-up PR
being late. If you have the majority of the content queued up
early enough and have a few more things or even just a single
fix later, that's not an issue at all.

     Arnd


      reply	other threads:[~2026-04-20 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  8:50 [GIT PULL] amlogic ARM64 DT updates for v7.1 Neil Armstrong
2026-04-11  9:32 ` Krzysztof Kozlowski
2026-04-13  7:10   ` Neil Armstrong
2026-04-13  7:17     ` Krzysztof Kozlowski
2026-04-13  7:27       ` Neil Armstrong
2026-04-13  7:30       ` Krzysztof Kozlowski
2026-04-13  7:45         ` Neil Armstrong
2026-04-13  7:48           ` Krzysztof Kozlowski
2026-04-20 15:25         ` Arnd Bergmann
2026-04-20 17:31           ` Neil Armstrong
2026-04-20 19:41             ` Arnd Bergmann [this message]

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=d95cfc82-327f-4bed-95ae-88a9182eedba@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox