From: Frank Scheiner <frank.scheiner@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com, cc@epic-linux.org
Subject: Re: [PATCH 6.6 0000/1226] 6.6.145-rc2 review
Date: Fri, 24 Jul 2026 11:25:04 +0200 [thread overview]
Message-ID: <e4b59f50-f0b9-4e7f-b0a3-b4cf8cd4f1d3@web.de> (raw)
In-Reply-To: <2026072447-chloride-plug-638e@gregkh>
On 24.07.26 08:17, Greg Kroah-Hartman wrote:
> On Thu, Jul 23, 2026 at 02:21:28PM +0200, Frank Scheiner wrote:
>> [...]
>> Of course we are hobbyists, we're doing it for the fun of it. If you
>> want to learn more, please head over to:
>>
>> https://epic-linux.org/
>
> Cool, but what happens when these last kernels with support for the
> platform goes end-of-life? While running things in emulators is fun,
> how will future userspace code that needs newer kernel features ever be
> possible?
Actually it is already possible:
Our autobuilder built and builds all current stable kernel versions.
The post 6.6 ones with patches on top (see e.g. [1]), like for mainline.
The stable kernels are also run-tested with Ski, which only requires a
few extra patches post linux-4.19.y depending on version ([2]). Also we
follow glibc and make it "work" for us ([3]).
[1]: https://github.com/linux-ia64/linux-stable-rc/tree/__mirror/patches
[2]: https://github.com/linux-ia64/ski/tree/hp-sim-for-linux
[3]: https://github.com/linux-ia64/glibc-ia64/
I hope I can get qemu-system-ia64 working in GHA in the future, so we
can also run-test non-Ski kernels there.
Mainline is also tested weekly (most of the time) on real hardware
([4]). So stable kernels post 6.6 always start in a working state. I
believe I even tested the older ones at least once on real hardware,
too.
[4]: https://epic-linux.org/#!machines/
Cheers,
Frank
next prev parent reply other threads:[~2026-07-24 9:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 14:33 Greg Kroah-Hartman
2026-07-22 15:01 ` Brett A C Sheffield
2026-07-22 17:25 ` Frank Scheiner
2026-07-23 7:46 ` Greg Kroah-Hartman
2026-07-23 9:33 ` Tomáš Glozar
2026-07-23 12:21 ` Frank Scheiner
2026-07-24 6:17 ` Greg Kroah-Hartman
2026-07-24 9:25 ` Frank Scheiner [this message]
2026-07-22 18:30 ` Florian Fainelli
2026-07-22 20:11 ` Pavel Machek
2026-07-23 8:37 ` Shung-Hsi Yu
2026-07-23 10:17 ` Greg Kroah-Hartman
2026-07-24 6:18 ` Greg Kroah-Hartman
2026-07-24 6:52 ` Shung-Hsi Yu
2026-07-24 7:58 ` Shung-Hsi Yu
2026-07-23 11:28 ` Miguel Ojeda
2026-07-23 14:30 ` Wentao Guan
2026-07-23 15:54 ` Mark Brown
2026-07-24 9:26 ` Peter Schneider
2026-07-23 9:53 Tomas Glozar
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=e4b59f50-f0b9-4e7f-b0a3-b4cf8cd4f1d3@web.de \
--to=frank.scheiner@web.de \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=cc@epic-linux.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®