From: "Arnd Bergmann" <arnd@arndb.de>
To: "Duje Mihanović" <dujemihanovic32@gmail.com>, soc@lists.linux.dev
Cc: "Karel Balej" <balejk@matfyz.cz>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] PXA1908 DT changes for 6.18
Date: Thu, 25 Sep 2025 23:06:23 +0200 [thread overview]
Message-ID: <d723fba3-1539-4728-951f-8697ecdf176c@app.fastmail.com> (raw)
In-Reply-To: <2398680.ElGaqSPkdT@radijator>
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
prev parent reply other threads:[~2025-09-25 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 16:52 [GIT PULL] PXA1908 DT changes for 6.18 Duje Mihanović
2025-09-24 21:41 ` Arnd Bergmann
2025-09-25 20:30 ` Duje Mihanović
2025-09-25 21:06 ` 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=d723fba3-1539-4728-951f-8697ecdf176c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=balejk@matfyz.cz \
--cc=dujemihanovic32@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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