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>
Subject: Re: [ANNOUNCE] 5.10.162-rt79
Date: Thu, 26 Jan 2023 18:41:27 +0100 [thread overview]
Message-ID: <2ad9f8a7528818b9509f62278b42e5bc6d210054.camel@siemens.com> (raw)
In-Reply-To: <Y9KOvZH61omPpn/3@uudg.org>
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.
>
> 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/
>
> You can get this release via the git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>
> branch: v5.10-rt
> Head SHA1: 10ea07eb47e2f5a82c5dabba993635c73c11592f
>
next prev parent reply other threads:[~2023-01-26 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 14:31 Luis Claudio R. Goncalves
2023-01-26 17:41 ` Florian Bezdeka [this message]
2023-02-23 14:33 ` Daniel Wagner
2023-03-03 8:29 ` Florian Bezdeka
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=2ad9f8a7528818b9509f62278b42e5bc6d210054.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=carnil@debian.org \
--cc=daniel.wagner@suse.com \
--cc=jan.kiszka@siemens.com \
--cc=jeffreyjbrady@gmail.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=markgross@kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/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®