From: Daniel Wagner <wagi@monom.org>
To: Pavel Machek <pavel@denx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>
Subject: Re: [ANNOUNCE] 4.19.261-rt116
Date: Tue, 15 Nov 2022 15:11:27 +0100 [thread overview]
Message-ID: <20221115141127.afwm534e47yj2ybb@carbon.lan> (raw)
In-Reply-To: <Y3KSiYf2WAct0Oks@duo.ucw.cz>
On Mon, Nov 14, 2022 at 08:10:01PM +0100, Pavel Machek wrote:
> https://www.kernel.org/pub/linux/kernel/projects/rt/4.19/older/patch-4.19.261-rt116.patch.xz
>
> Thank you, I'll take a look.
>
> Just out of curiosity, what happened to -rt115? I see announcements
> for -rt114 and then -rt116.
When we (stable-rt maintainers) do the updates we tag all merges which
had a conflict. So in this case when I updated from 4.19.255 to
4.19.261, there was merge conflict in 4.19.257:
Merge tag 'v4.19.257' into v4.19-rt
This is the 4.19.257 stable release
Conflicts:
net/core/dev.c
We do this to make it more obvious when we need to touch code by hand
which makes any verification later on simpler. But these intermediated
steps are not separately announced/released. There are available in the
git tree but not as tar files.
prev parent reply other threads:[~2022-11-15 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 19:03 Daniel Wagner
2022-11-14 19:10 ` Pavel Machek
2022-11-14 19:29 ` Pavel Machek
2022-11-15 14:14 ` Daniel Wagner
2022-11-16 10:04 ` Pavel Machek
2022-11-15 14:11 ` Daniel Wagner [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=20221115141127.afwm534e47yj2ybb@carbon.lan \
--to=wagi@monom.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.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®