From: Krzysztof Kozlowski <krzk@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: arm-soc <arm@kernel.org>, soc <soc@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com
Subject: Re: [GIT,PULL,1/2] MediaTek ARM64 Device Tree updates for v7.1
Date: Tue, 24 Mar 2026 14:54:27 +0100 [thread overview]
Message-ID: <d90284c1-3d54-4072-961b-6bb77f845ad4@kernel.org> (raw)
In-Reply-To: <b8b9ad39-0e9e-4c38-b080-85153b2a66d1@collabora.com>
On 24/03/2026 14:52, AngeloGioacchino Del Regno wrote:
>> Days in linux-next:
>> ----------------------------------------
>> 0 | +++ (3)
>>
>> With 0 days in next, you cannot really react on any bug reports.
>>
>
> OUCH!!!
>
> Sorry about that, I didn't notice that my for-next didn't get pushed when I tried
> to actually push it (and I was 100% convinced that I had checked after pushing).
>
> Krzysztof, thanks for making me notice, that was completely unintentional.
>
> I re-pushed the for-next branch exactly a second ago; that should give it some good
> time in -next ... or well, otherwise, we can always delay those commits for v7.2 or
> for fixes.
There is still plenty of time for this cycle, so no worries.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-24 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 8:56 [GIT,PULL,1/2] MediaTek ARM64 Device Tree updates for v7.1 AngeloGioacchino Del Regno
2026-03-20 8:56 ` [GIT,PULL,2/2] MediaTek ARM32 " AngeloGioacchino Del Regno
2026-03-21 11:07 ` [GIT,PULL,1/2] MediaTek ARM64 " Krzysztof Kozlowski
2026-03-24 13:52 ` AngeloGioacchino Del Regno
2026-03-24 13:54 ` Krzysztof Kozlowski [this message]
2026-03-27 11:48 ` Krzysztof Kozlowski
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=d90284c1-3d54-4072-961b-6bb77f845ad4@kernel.org \
--to=krzk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--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