public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com
Subject: Re: [ANNOUNCE] v4.4.302-cip97-rt54
Date: Fri, 2 May 2025 12:17:29 +0200	[thread overview]
Message-ID: <aBSbubCPJRhuN3Ll@duo.ucw.cz> (raw)
In-Reply-To: <a8f99b04-2587-4d8d-ace9-a8b9b32122c6@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

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.4.y-cip-rt
> > https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt-rebase
> > 
> > This does not yet have fixes for "Repeated WARNINGs in
> > unpin_current_cpu()". I'll work on those next.
> 
> I suppose this update will also lift the baseline to the recent 4.4
> release, right? I only now realized that this was using the 4.4-cip
> version from March, rather than recent cip98. Why?

Yes, new version should be out. I believe that's how timing worked
out.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2025-05-02 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 18:47 [ANNOUNCE] v4.4.302-cip97-rt54 Pavel Machek
2025-05-02  8:29 ` Jan Kiszka
2025-05-02 10:17   ` 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=aBSbubCPJRhuN3Ll@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