linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tiejun Chen <tiejunc@vmware.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Julia Cartwright <julia@ni.com>,
	Daniel Wagner <daniel.wagner@siemens.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: RE: [ANNOUNCE] 4.14.63-rt40
Date: Thu, 23 Aug 2018 09:31:09 +0000	[thread overview]
Message-ID: <CY1PR0501MB14666E51F4D066F2E0C5208AC5370@CY1PR0501MB1466.namprd05.prod.outlook.com> (raw)
In-Reply-To: <20180822141458.0b6b6af7@gandalf.local.home>

Steven,

commit 7f11a591bbdb111792298144c3476506aa7f1ca8 (HEAD -> v4.14.63-rt40-rebase, tag: v4.14.63-rt40-rebase, origin/v4.14-rt-rebase)
Author: Steven Rostedt (VMware) <rostedt@goodmis.org>
Date:   Wed May 16 09:33:00 2018 -0400

    Linux 4.14.63-rt40 REBASE

diff --git a/localversion-rt b/localversion-rt
index 90290c642ed5..a3b2408c1da6 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
--rt29
+-rt37
    ^
Isn't it supposed to be rt40?

Thanks
Tiejun

> -----Original Message-----
> From: linux-rt-users-owner@vger.kernel.org <linux-rt-users-
> owner@vger.kernel.org> On Behalf Of Steven Rostedt
> Sent: Thursday, August 23, 2018 2:15 AM
> To: LKML <linux-kernel@vger.kernel.org>; linux-rt-users <linux-rt-
> users@vger.kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>; Carsten Emde
> <C.Emde@osadl.org>; John Kacur <jkacur@redhat.com>; Sebastian Andrzej
> Siewior <bigeasy@linutronix.de>; Julia Cartwright <julia@ni.com>; Daniel
> Wagner <daniel.wagner@siemens.com>; Tom Zanussi
> <tom.zanussi@linux.intel.com>
> Subject: [ANNOUNCE] 4.14.63-rt40
> 
> 
> Dear RT Folks,
> 
> I'm pleased to announce the 4.14.63-rt40 stable release.
> 
> 
> This release is just an update to the new stable 4.14.63 version and no RT
> specific changes have been made.
> 
> NOTE: There is a known issue with this release. The fix is here:
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flkml.ker
> nel.org%2Fr%2F1534660115.6187.4.camel%40gmx.de&amp;data=02%7C01%
> 7Ctiejunc%40vmware.com%7Cf5505a126bb8491ac2db08d6085b2e15%7Cb39
> 138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636705585062142956&amp
> ;sdata=vdH9xCIjC2pVwMggGJvVAkfIrq2jG3qJaTi0asnq7Sk%3D&amp;reserved
> =0
> 
> I did not apply it to this release because it needs to be added to v4.16-rt first
> before it gets backported. Feel free to apply it yourself if you have any
> concerns.
> 
> 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: v4.14-rt
>   Head SHA1: da6bee3cef4af60566dc56f3d48fce0b18165107
> 
> 
> Or to build 4.14.63-rt40 directly, the following patches should be applied:
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ke
> rnel.org%2Fpub%2Flinux%2Fkernel%2Fv4.x%2Flinux-
> 4.14.tar.xz&amp;data=02%7C01%7Ctiejunc%40vmware.com%7Cf5505a126bb
> 8491ac2db08d6085b2e15%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7
> C0%7C636705585062152970&amp;sdata=cuTUJOzPb8rJSbK8QLfqb5s9jHNYk3
> WbrUDla5s6ixM%3D&amp;reserved=0
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ke
> rnel.org%2Fpub%2Flinux%2Fkernel%2Fv4.x%2Fpatch-
> 4.14.63.xz&amp;data=02%7C01%7Ctiejunc%40vmware.com%7Cf5505a126bb
> 8491ac2db08d6085b2e15%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7
> C0%7C636705585062152970&amp;sdata=yVr3le4J2mYik%2B8MJ796KcEb%2B
> 7i%2BhAkEWQt2qZ5q2KY%3D&amp;reserved=0
> 
> 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ke
> rnel.org%2Fpub%2Flinux%2Fkernel%2Fprojects%2Frt%2F4.14%2Fpatch-
> 4.14.63-
> rt40.patch.xz&amp;data=02%7C01%7Ctiejunc%40vmware.com%7Cf5505a126
> bb8491ac2db08d6085b2e15%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1
> %7C0%7C636705585062152970&amp;sdata=TEcL3d3nkG623UFOgWZV5wkrJl
> oPsY7qXcZ8bm%2FmFDI%3D&amp;reserved=0
> 
> 
> 
> 
> Enjoy,
> 
> -- Steve


  reply	other threads:[~2018-08-23  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 18:14 [ANNOUNCE] 4.14.63-rt40 Steven Rostedt
2018-08-23  9:31 ` Tiejun Chen [this message]
2018-08-24  0:32   ` Steven Rostedt
2018-08-24 16:14 ` Bernhard Landauer
2018-08-24 16:17   ` Steven Rostedt
2018-08-28  2:41     ` Steven Rostedt
2018-08-28 11:49       ` Bernhard Landauer

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=CY1PR0501MB14666E51F4D066F2E0C5208AC5370@CY1PR0501MB1466.namprd05.prod.outlook.com \
    --to=tiejunc@vmware.com \
    --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;
as well as URLs for NNTP newsgroup(s).