From: Daniel Wagner <wagi@monom.org>
To: 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>,
Daniel Wagner <daniel.wagner@siemens.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Julia Cartwright <julia@ni.com>
Subject: Re: [ANNOUNCE] 4.4.162-rt175
Date: Tue, 30 Oct 2018 14:25:48 +0100 [thread overview]
Message-ID: <892f6f12-d8a9-2570-edff-ba077344bc63@monom.org> (raw)
In-Reply-To: <20181029200501.BECE75007F3@mail.monom.org>
On 29/10/2018 21:04, Daniel Wagner wrote:
> Hello RT Folks!
>
> I'm pleased to announce the 4.4.162-rt175 stable release.
>
> This release is just an update to the new stable 4.4.120 version
> and no RT specific changes have been made.
>
> This version still qspinlock enabled, because I wanted to update first
> to the last stable release and then resend the patch which drops back
> to ticket spinlocks.
I forgot to mention about the tagging/counting policy change. The
stable-rt maintainers have decided to use the same tagging/counting
strategy for all the stable-rt trees. If there is no merge conflict the
latest stable release is merged and tagged. All intermediates merge
commit and tag is not done anymore unless there is a conflict. The
conflict will be resolved and a merge commit with tag will be applied.
Thanks,
Daniel
prev parent reply other threads:[~2018-10-30 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 20:04 [ANNOUNCE] 4.4.162-rt175 Daniel Wagner
2018-10-30 13:25 ` 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=892f6f12-d8a9-2570-edff-ba077344bc63@monom.org \
--to=wagi@monom.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.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