From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com
Subject: Re: [ANNOUNCE] 4.19.233-cip69-rt24 (-rt105)
Date: Tue, 15 Mar 2022 19:36:26 +0100 [thread overview]
Message-ID: <20220315183626.GA30901@duo.ucw.cz> (raw)
In-Reply-To: <2cd7693d-dc31-f378-e309-26b019404f2b@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Tue 2022-03-15 07:13:31, Jan Kiszka wrote:
> On 15.03.22 00:21, Pavel Machek wrote:
> > Hi!
> >
> > New realtime trees should be available at kernel.org.
> >
> > Trees are available at
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt
> > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase
> >
> > And their content should be identical.
> >
> > Note that there are speculation-related bug fixes in the pipeline. If
> > you are using complex out-of-order CPUs for dealing with secret data
> > a) please stop, b) let us know and c) be sure to install next update.
> >
>
> You tagging script seem to have run amok with "v": ;)
>
> * [new tag] vv4.19.233-cip69-rt24 -> vv4.19.233-cip69-rt24
> * [new tag] vv4.19.233-cip69-rt24-rebase -> vv4.19.233-cip69-rt24-rebase
Thanks for report, and sorry about that. It should be fixed now.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-03-15 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 23:21 [ANNOUNCE] 4.19.233-cip69-rt24 (-rt105) Pavel Machek
2022-03-15 6:13 ` Jan Kiszka
2022-03-15 18:36 ` Pavel Machek [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=20220315183626.GA30901@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.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