From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@lists.linux.dev>
Subject: Re: dovetail kernel maintenance
Date: Mon, 11 Mar 2024 22:30:16 +0100 [thread overview]
Message-ID: <87il1stpd4.fsf@xenomai.org> (raw)
In-Reply-To: <7d95d478-2f28-4ecb-8f59-b59758a20597@siemens.com>
Jan Kiszka <jan.kiszka@siemens.com> writes:
> On 06.03.24 09:41, Philippe Gerum wrote:
>>
>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>
>>> On 21.02.24 19:30, Jan Kiszka wrote:
>>>> Hi Philippe,
>>>>
>>>> people started to ask about updates for our kernel trees, and you
>>>> mentioned to me before that you would focus on the last two LTS kernels.
>>>> Right now, there are to-be-tagged updated sleeping in 6.1 and 6.6 but
>>>> then also in 5.10 (all referring to the -rebase branches). Before taking
>>>> over 5.10 and 5.15, I would like to clarify their state. But I would
>>>> also like to know what is delaying the tagging of 6.1 and 6.6.
>>>>
>>>
>>> Gentle ping for this question.
>>>
>>
>> Well, my posts to the mailing list from my usual address have been
>> rejected a couple of weeks ago due to smtp authentication issues it
>> seems, which are now (mostly) sorted out, I thought you did receive this
>> reply as a direct recipient though. Looks like you did not. So here it
>> is.
>>
>> PS: Since this reply was written, the x86 status with respect to the
>> Dovetail port to v6.8-rc7 has improved. Still in the process of
>> rewriting the arm64/fpsimd stuff.
>>
>
> Let us know where exactly help could be provided. I just want to avoid
> duplicate attempts, so the development should be coordinated publicly.
>
Addressing [1] comes to mind. As I said in this thread, one could use
the same logic which allows x86 to support preemption of the helpers for
in-kernel fpu by the real-time core. However, I have to upgrade the
basic arm64/fpsimd port to v6.8 before someone else can handle this
task. ETA, hopefully next week.
>>> From: Philippe Gerum <rpm@xenomai.org>
>>> Subject: Re: dovetail kernel maintenance
>>> To: Jan Kiszka <jan.kiszka@siemens.com>
>>> Cc: Xenomai <xenomai@lists.linux.dev>
>>> Date: Wed, 21 Feb 2024 21:00:17 +0100
>>>
>>>
>>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>>
>>>> Hi Philippe,
>>>>
>>>> people started to ask about updates for our kernel trees, and you
>>>> mentioned to me before that you would focus on the last two LTS kernels.
>>>> Right now, there are to-be-tagged updated sleeping in 6.1 and 6.6 but
>>>> then also in 5.10 (all referring to the -rebase branches). Before taking
>>>> over 5.10 and 5.15, I would like to clarify their state.
>>>
>>> Dovetail ports to 5.10 and 5.15 are not maintained anymore, although I'm
>>> still upgrading 5.10 from time to time for work-related reasons, but
>>> nobody should expect this to last for long.
>>>
>
> I can take over those two, but we should coordinate that to avoid
> parallel updates, at least of 5.10. As 5.15 is dropped already, I would
> grab it now officially. Still need to decide whether I continue the
> rebase branches, though.
I don't plan to merge the generic support for oob networking (in
net/core/) which underlies the UDP implementation for xenomai4. So I'm
fine with handing over the maintenance of v5.10 asap.
[1] https://lore.kernel.org/xenomai/ff580dec-096d-45cb-b906-527446c4fa87@163.com/T/#t
--
Philippe.
next prev parent reply other threads:[~2024-03-11 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 18:30 dovetail kernel maintenance Jan Kiszka
2024-03-06 7:05 ` Jan Kiszka
2024-03-06 8:41 ` Philippe Gerum
2024-03-07 8:07 ` Jan Kiszka
2024-03-11 21:30 ` Philippe Gerum [this message]
2024-03-17 21:04 ` Philippe Gerum
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=87il1stpd4.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.