[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <d723fba3-1539-4728-951f-8697ecdf176c@app.fastmail.com>
Date: Thu, 25 Sep 2025 23:06:23 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: Duje Mihanović <dujemihanovic32@...il.com>,
soc@...ts.linux.dev
Cc: "Karel Balej" <balejk@...fyz.cz>, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] PXA1908 DT changes for 6.18
On Thu, Sep 25, 2025, at 22:30, Duje Mihanović wrote:
> On Wednesday, 24 September 2025 23:41:17 Central European Summer Time Arnd
> Bergmann wrote:
>> If you can send an updated pull request based on -rc1, I'll
>> try to do find the time to merge that, otherwise please
>> rebase on 6.18-rc1 once that is out.
>
> I don't want to rush anything, I'd rather wait until after the v6.18 merge
> window then unless the merge itself is very trivial.
>
> My only question then would be whether I could still target v6.18 or would
> that postpone the series for v6.19? I don't really mind the latter, I'd just
> like to know.
I meant sending a pull request for 6.19 based on 6.18-rc1.
Generally speaking, I need pull requests to be based
on an -rc release that is no newer than the one I'm
already using in the tree, so -rc1 is what you can
use to be on the safe side.
You can also send multiple pull requests during a
cycle if you either want to add more contents or find
bugs in the earlier patches. This way you can ensure
that there is enough time to fix up mistakes if you
send something at first that for some reason needs
a rework.
Arnd
Powered by blists - more mailing lists