From: Frank Scheiner <frank.scheiner@web.de>
To: torvalds@linux-foundation.org
Cc: "Tomáš Glozar" <tglozar@gmail.com>,
"Sergei Trofimovich" <slyich@gmail.com>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-ia64@vger.kernel.org, t2@t2sde.org
Subject: Re: Linux 6.12
Date: Wed, 20 Nov 2024 16:29:59 +0100 [thread overview]
Message-ID: <775f2bd5-5567-4da2-9b79-8f2e7fc9b38a@web.de> (raw)
In-Reply-To: <CAHk-=wgtGkHshfvaAe_O2ntnFBH3EprNk1juieLmjcF2HBwBgQ@mail.gmail.com>
Dear all,
here comes the usual update on Linux/ia64 for v6.12:
We're already past mid November, so it looks like we're doing this now
since over a year actually. Maybe a good occasion to go through some of
the highlights during this time frame:
* Six mainline releases v6.7 - v6.12, all running on the ia64 hardware
we have available for testing ([1]). Not to speak of all the RCs and
test builds during merge windows tested in between. To have a
forward-look on possible build problems between RCs and during merge
windows an auto-builder for Linux mainline was set up, that builds
mainline for ia64 each day. This also shortens the time frame for us to
check for a cause when problems arise.
[1]: http://epic-linux.org/#!testing-effort/tested-kernels-table.md
* The hp-sim platform was reinstated for Linux up to mainline, allowing
everybody to run ia64 software (kernels and userland) on non-ia64
hardware, thanks to ski maintained by Sergei Trofimovich. This is for
example used for our Linux stable R(C) auto-builder to test-boot each
kernel after it was built and run some userland tools for a test. By
involving ski for this auto-builder it can not only demonstrate build
problems, but also problems during runtime, as shown already in the
corresponding issues ([2]).
[2]: https://github.com/linux-ia64/linux-stable-rc/issues
* Two Linux distributions keep support for ia64: T2/SDE ([3]) and EPIC
Slack [(4)].
[3]: https://t2sde.org/
[4]: http://epic-slack.org/
* Also http://epic-linux.org/ was established to allow interested people
to find current and relevant information about Linux/ia64 at a central
place.
Maybe someone can help me here with the history, but was there another
architecture that has been kicked out of the kernel, that received that
level of continuation afterwards?
We'll see where this goes.
Find the last Linux/ia64 update on [5].
[5]: https://lore.kernel.org/lkml/5d1b5880-9bdc-4b04-81dc-341df7b02177@web.de/
****
Thank you all for your hard work on Linux!
Cheers,
Frank et al
next prev parent reply other threads:[~2024-11-20 15:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 22:26 Linus Torvalds
2024-11-19 8:48 ` Build regressions/improvements in v6.12 Geert Uytterhoeven
2024-11-19 8:52 ` Geert Uytterhoeven
2024-11-20 15:29 ` Frank Scheiner [this message]
2024-11-27 6:46 ` TPM/EFI issue [Was: Linux 6.12] Jiri Slaby
2024-11-27 16:24 ` James Bottomley
2024-11-28 7:20 ` Jiri Slaby
2024-11-28 16:13 ` James Bottomley
2024-11-29 6:36 ` Jiri Slaby
2024-11-29 16:03 ` James Bottomley
2024-11-29 21:08 ` James Bottomley
2024-12-02 7:56 ` Jiri Slaby
2024-11-30 7:52 ` Jiri Slaby
2024-11-30 2:49 ` Jarkko Sakkinen
2024-11-30 2:52 ` Jarkko Sakkinen
2024-12-02 7:52 ` Jiri Slaby
2024-12-07 12:16 ` Jarkko Sakkinen
2024-12-09 6:43 ` Jiri Slaby
2024-12-09 12:54 ` Jarkko Sakkinen
2024-12-10 6:13 ` Jiri Slaby
2024-12-10 13:04 ` James Bottomley
2024-12-14 3:54 ` Jarkko Sakkinen
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=775f2bd5-5567-4da2-9b79-8f2e7fc9b38a@web.de \
--to=frank.scheiner@web.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slyich@gmail.com \
--cc=t2@t2sde.org \
--cc=tglozar@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®