linux-kernel - Re: [PATCH v6 0/7] RK3576 thermal sensor support, including OTP trim adjustments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2664626.Lt9SDvczpP@diego>
Date: Thu, 31 Jul 2025 15:45:47 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Sebastian Reichel <sebastian.reichel@...labora.com>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
 Alexey Charkov <alchark@...il.com>,
 Nicolas Frattaroli <nicolas.frattaroli@...labora.com>,
 "Rafael J. Wysocki" <rafael@...nel.org>, Zhang Rui <rui.zhang@...el.com>,
 Lukasz Luba <lukasz.luba@....com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Jonas Karlman <jonas@...boo.se>, kernel@...labora.com,
 linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Ye Zhang <ye.zhang@...k-chips.com>
Subject: Re: [PATCH v6 0/7] RK3576 thermal sensor support,
 including OTP trim adjustments

Am Donnerstag, 31. Juli 2025, 15:27:03 Mitteleuropäische Sommerzeit schrieb Sebastian Reichel:
> Hi,
> 
> On Thu, Jul 31, 2025 at 10:11:23AM +0200, Heiko Stübner wrote:
> > Right now we're in the middle of the merge-window though, so everything
> > I apply now, I'd need to rebase onto -rc1 in slightly more than a week,
> > invalidating all those nice commit hashes that end up in the "applied" mails.
> > 
> > So I'm struggling with myself on every merge window about that.
> 
> Your are not supposed to merge anything to your for-next branch
> during the merge window anyways. See first sentence of Stephen
> Rothwell's mails [0]:
>
> > Please do not add any v6.18 material to your linux-next included
> > branches until after v6.17-rc1 has been released.

The general idea is just merging but without updating the -next branch,
then after -rc1 rebase + do new -next.

But as you pointed out, this is all cumbersome and doesn't shave off much
from the amount of patches waiting, so as most of the time, I'll just wait
for -rc1 to start clean :-)

> 
> [0] https://lore.kernel.org/all/20250731133311.1a3e3867@canb.auug.org.au/
> 
> Greetings,
> 
> -- Sebastian
>