Message-ID: <2ad9f8a7528818b9509f62278b42e5bc6d210054.camel@siemens.com>
Subject: Re: [ANNOUNCE] 5.10.162-rt79
From:   Florian Bezdeka <florian.bezdeka@siemens.com>
To:     "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        linux-rt-users <linux-rt-users@vger.kernel.org>,
        stable-rt <stable-rt@vger.kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Carsten Emde <C.Emde@osadl.org>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        Daniel Wagner <daniel.wagner@suse.com>,
        Tom Zanussi <tom.zanussi@linux.intel.com>,
        Clark Williams <williams@redhat.com>,
        Mark Gross <markgross@kernel.org>,
        Pavel Machek <pavel@denx.de>,
        Jeff Brady <jeffreyjbrady@gmail.com>,
        Salvatore Bonaccorso <carnil@debian.org>,
        Mark Rutland <mark.rutland@arm.com>
Cc:     Jan Kiszka <jan.kiszka@siemens.com>
Date:   Thu, 26 Jan 2023 18:41:27 +0100
In-Reply-To: <Y9KOvZH61omPpn/3@uudg.org>
References: <Y9KOvZH61omPpn/3@uudg.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Feedback-ID: 519:519-68982:519-21489:flowmailer
Precedence: bulk

Hi all, especially to stable-rt maintainers,

On Thu, 2023-01-26 at 11:31 -0300, Luis Claudio R. Goncalves wrote:
> I'm pleased to announce the 5.10.162-rt79 stable release.
>=20
> This release contains a single change, a fix to the aarch64 build failure
> I introduced while fixing merge conflicts in 5.10.162-rt78.

The CIP (see [1] for technical infos about CIP) kernel maintainers
(especially Pavel) noticed this build failure while trying to prepare
the next 5.10 based rt-cip release.

Looking at the kernel CI logs [2] this build failure was detected by
kernel-ci as well but it seems the build result did not make it back to
the maintainers. Is that correct?

From the CIP projects perspective we would like to improve the
situation.

From my perspective the following could be done:

  - Instead of (or in addition to) building and testing released -rt
    branches enable testing of -rt release candidates
  - Make sure the build results get back to the maintainers

I'm not sure if every -rt branch has a -rc branch. I'm not familiar
with the -rt release process yet.

What do you think? Does that make sense?

The discussion did not start yet, but it might be possible that I'm
able to do such kernel-ci improvements under the CIP umbrella.

Best regards,
Florian

[1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/start
[2] https://linux.kernelci.org/build/rt-stable/branch/v5.10-rt/kernel/v5.10=
.162-rt78/

>=20
> You can get this release via the git tree at:
>=20
>   git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>=20
>   branch: v5.10-rt
>   Head SHA1: 10ea07eb47e2f5a82c5dabba993635c73c11592f
>=20