All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Scheiner <frank.scheiner@web.de>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, "Tomáš Glozar" <tglozar@gmail.com>
Subject: Re: Linux 6.14-rc1
Date: Wed, 5 Feb 2025 11:51:52 +0100	[thread overview]
Message-ID: <74f9a401-44ca-4d56-83b4-459ac6bca598@web.de> (raw)
In-Reply-To: <CAHk-=wicYNCkEgH06w0mpR+GJhJ_ywe0BLTTFXBAj1+y0dqe4Q@mail.gmail.com>

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


      parent reply	other threads:[~2025-02-05 10:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  0:26 Linux 6.14-rc1 Linus Torvalds
2025-02-03  3:07 ` linus-next: stats (Was: Linux 6.14-rc1) Stephen Rothwell
2025-02-03 15:58 ` Linux 6.14-rc1 Guenter Roeck
2025-02-05 18:55   ` Kees Cook
2025-02-05 10:51 ` Frank Scheiner [this message]

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=74f9a401-44ca-4d56-83b4-459ac6bca598@web.de \
    --to=frank.scheiner@web.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.