[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74f9a401-44ca-4d56-83b4-459ac6bca598@web.de>
Date: Wed, 5 Feb 2025 11:51:52 +0100
From: Frank Scheiner <frank.scheiner@....de>
To: torvalds@...ux-foundation.org
Cc: linux-kernel@...r.kernel.org, Tomáš Glozar
<tglozar@...il.com>
Subject: Re: Linux 6.14-rc1
Dear Linus,
> Two weeks have passed, and the merge window is over.
>
> This is actually a _tiny_ merge window, and that's ok.
I can confirm, that this merge window required much less involvement
than the last one. It actually felt a little unreal - compared to last
time - to see our mainline autobuilder succeed that often during a merge
window w/o updating the ia64 patch set.
Let's do it like that more often. (-;
****
So, as can be seen in our logbook ([1]) and kernel table ([2]) - after
making the required adaptations (everything after c15d28e on [3]) -
v6.14-rc1 is running well and there were no regressions observed for the
things that are regularly tested:
* boot to login and small package build in T2 (rx2620, rx2660, rx4640,
rx6600)
* boot to login and building the "weekly" package updates from Slackware
for EPIC Slack (rx2800 i2)
* booting in Ski and a `7za` benchmark run (hp-sim)
[1]: http://epic-linux.org/#!testing-effort/log.md#2025-02-03
[2]: http://epic-linux.org/#!testing-effort/tested-kernels-table.md#v6.14-rc1
[3]: https://github.com/johnny-mnemonic/linux-ia64/commits/v6.14-rc1-w-ia64/
As "always" the v6.14-rc1 builds happen with the latest GCC snapshot
available and - since binutils had a new release in the meantime -
version 2.44 was also used during the builds w/o observable problems.
****
I'm pretty sure I will regret it, but if time allows I'll try to extend
testing also to on-disk installations during this cycle.
Cheers,
Frank
Powered by blists - more mailing lists