linux-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tomáš Glozar" <tglozar@gmail.com>
To: linux-ia64@vger.kernel.org
Cc: Frank Scheiner <frank.scheiner@web.de>
Subject: [ANNOUNCE] Linux v6.16-epic1
Date: Mon, 8 Sep 2025 23:24:23 +0200	[thread overview]
Message-ID: <CAHtyXDernSaNUtXas_nO+VR8NiBghoJgn=bfcta7fGpJDOiVOg@mail.gmail.com> (raw)

Hello linux-ia64!

It's time to bump up the version, and get the EPIC code up to date
with latest upstream! Of course, reverts of some bits and pieces of
code that is needed by Itanium still have to be done, but they are
sparse at this point, and the process is mostly painless: four whole
upstream versions were successfully merged over an extended weekend,
with some minimal help from parallel johnny-mnemonic fork.

With this release, a new commit model is adopted: upstream is merged
into the fork at relevant tags. This allows to push normally into the
master-epic branch, and track which linux-ia64 patches were applied
after the merge of which upstream release. New branches will no longer
be created for upstream releases.

Known issues:

- See https://github.com/linux-ia64/linux-ia64/issues

Fixes:

- None

Some changes in tools/ and scripts/ had Itanium-specific code removed.
This is not addressed yet in this release. Also, unimplemented
syscalls are piling up, so it's nearly time for to make that up to
date.

As always, the release can be obtained in patch or whole source code
from our repo, at:
https://github.com/linux-ia64/linux-ia64/releases/tag/v6.16-epic1

Tomáš

                 reply	other threads:[~2025-09-08 21:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAHtyXDernSaNUtXas_nO+VR8NiBghoJgn=bfcta7fGpJDOiVOg@mail.gmail.com' \
    --to=tglozar@gmail.com \
    --cc=frank.scheiner@web.de \
    --cc=linux-ia64@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).