From: David Runge <dave@sleepmap.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: v6.0.3-rt12 does not compile (WAS: [ANNOUNCE] v6.1-rc2-rt1)
Date: Tue, 15 Nov 2022 18:07:09 +0100 [thread overview]
Message-ID: <Y3PHQM0QXTTrKcXg@hmbx> (raw)
In-Reply-To: <Y1osx2Iw0qs3gWxu@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On 2022-10-27 09:01:27 (+0200), Sebastian Andrzej Siewior wrote:
> Please keep the list in Cc:
Thanks, will keep that in mind for the future!
> I'm going to release -rt13 in a bit with this fixed.
> There are few options like SLAB or TRANSPARENT_HUGEPAGE which are not
> available on PREEMPT_RT for one reason or another. I try to avoid
> dropping options if possible.
Seems I forgot to reply...
Thanks for releasing a new version so fast and being on top of these
changes!
For reference: Will there be more rebases on stable versions of the most
recent kernel versions going forward?
The linux-stable-rt repository seems to only cover LTS kernels AFAIKT
and a few more releases in the current stable kernel version range would
allow downstreams to more easily backport patches (e.g. for security
issues) also for the realtime kernel.
Best,
David
--
https://sleepmap.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-15 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 15:18 [ANNOUNCE] v6.1-rc2-rt1 Sebastian Andrzej Siewior
[not found] ` <Y1m0MXDKt0yqXdsu@hmbx>
2022-10-27 7:01 ` v6.0.3-rt12 does not compile (WAS: [ANNOUNCE] v6.1-rc2-rt1) Sebastian Andrzej Siewior
2022-11-15 17:07 ` David Runge [this message]
2022-11-17 7:44 ` Sebastian Andrzej Siewior
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=Y3PHQM0QXTTrKcXg@hmbx \
--to=dave@sleepmap.de \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.