From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Tobias Schaffner <tobias.schaffner@siemens.com>,
xenomai@lists.linux.dev
Subject: Re: Dovetail/Evl confusion on my end
Date: Tue, 07 Jul 2026 16:25:59 +0200 [thread overview]
Message-ID: <877bn6vpu0.fsf@xenomai.org> (raw)
In-Reply-To: <87o6givqdi.fsf@xenomai.org> (Philippe Gerum's message of "Tue, 07 Jul 2026 16:14:17 +0200")
Philippe Gerum <rpm@xenomai.org> writes:
> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
>
>> Hi Philippe,
>>
>> I just recognized that you updated the source of my rebase branches
>> meanwhile, so v7.0-dovetail-rebase (for dovetail) and next/v7.0-evl-
>> rebase for evl.
>>
>> While syncing the missing pieces I noticed that commit
>> ad7e492ff2 ("/dev/{null, zero}: dovetail: drop deprecated .write handler ")
>> is part of v7.0-evl-rebase but is not part of v7.0-dovetail-rebase.
>>
>> Why is that? Any specific reason?
>>
>
> I pushed this patch yesterday, and wanted to have some hindsight about
> it for a couple of (testing) days of the evl tree. I believe it is
> correct, but given the patched area, better safe than sorry. I plan to
> merge it last on top of 7.0-dovetail.
To elaborate a bit more, this patch only helps evl strictly speaking, by
preventing stdout/err redirections through proxies to cause a kernel
warning, which in fact reveals that some portion of the upstream code
(namely the /null and /zero cdevs at least) are still using a deprecated
file_operations handler, which the VFS complains about when using the
kernel interface to write to them.
--
Philippe.
next prev parent reply other threads:[~2026-07-07 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 13:56 Dovetail/Evl confusion on my end Florian Bezdeka
2026-07-07 14:14 ` Philippe Gerum
2026-07-07 14:25 ` Philippe Gerum [this message]
2026-07-07 15:02 ` Philippe Gerum
2026-07-07 22:00 ` Florian Bezdeka
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=877bn6vpu0.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@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.