linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: Pavel Machek <pavel@ucw.cz>
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>,
	Pavel Machek <pavel@denx.de>
Subject: Re: [ANNOUNCE] 4.4.277-rt224
Date: Fri, 20 Aug 2021 13:07:16 +0200	[thread overview]
Message-ID: <20210820110716.zmh7te5dvmndssgm@carbon.lan> (raw)
In-Reply-To: <20210820104328.GA30359@amd>

On Fri, Aug 20, 2021 at 12:43:28PM +0200, Pavel Machek wrote:
> > Sorry for the long delay. I was refactoring and improving my test
> > setup which took a bit longer than I expected. I switched from a
> > Debian based rootfs to an Tumbleweed based one, for obvious
> > reasons. Anyway, this should not matter at all.
> 
> A bit late thanks for the release, BTW. We are maintaining -cip-rt
> based kernels, and were getting worried :-).

Sorry about that. I should have send out a note earlier. Anyway, I'll
plan to work on the next update soon. There are a few futex changes
which collide. It's going to be interesting.

BTW, as you certainly are aware, the v4.4 kernel is EOL soon. As I
understand the CIP is going to take over the maintenance. So I assume
you are going to care of the -rt version as well?

  reply	other threads:[~2021-08-20 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  6:39 [ANNOUNCE] 4.4.277-rt224 Daniel Wagner
2021-08-20 10:43 ` Pavel Machek
2021-08-20 11:07   ` Daniel Wagner [this message]
2021-08-20 17:53     ` Pavel Machek
2021-08-26  8:42       ` Daniel Wagner

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=20210820110716.zmh7te5dvmndssgm@carbon.lan \
    --to=dwagner@suse.de \
    --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=pavel@ucw.cz \
    --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;
as well as URLs for NNTP newsgroup(s).