From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driver-core@lists.linux.dev, linux-rt-devel@lists.linux.dev,
linux-rt-users@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Clark Williams <williams@redhat.com>,
Danilo Krummrich <dakr@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [RFC PATCH] sysfs: Add /sys/kernel/realtime entry
Date: Fri, 10 Jul 2026 18:01:20 +0200 [thread overview]
Message-ID: <ae96c274f166301aba762d97caccddf176ad7968.camel@siemens.com> (raw)
In-Reply-To: <20260710115145.32729a7c@gandalf.local.home>
On Fri, 2026-07-10 at 11:51 -0400, Steven Rostedt wrote:
> On Fri, 10 Jul 2026 09:23:16 +0200
> Florian Bezdeka <florian.bezdeka@siemens.com> wrote:
>
> > uname might qualify, yes, but keep in mind that this sysfs based API is
> > already used, so a removal might break applications. Yes, userspace can
> > be fixed / adjusted, but it remains bad style, no?
>
> Then at most it will likely just stay in the -rt patch set. As it was never
> mainlined, it's not breaking any user space that uses only the mainline
> kernel.
>
Depends on what you consider a valid update scenario. Updating from 6.1-
rt with sysfs available to something like 6.18 (no sysfs anymore) will
still break - as long as you do not (force) update userspace in
lockstep.
I learned meanwhile that our detection moved to uname meanwhile, so this
is not a problem for us anymore.
Florian
next prev parent reply other threads:[~2026-07-10 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 14:31 [RFC PATCH] sysfs: Add /sys/kernel/realtime entry Sebastian Andrzej Siewior
2026-07-09 14:38 ` sashiko-bot
2026-07-09 14:46 ` Greg Kroah-Hartman
2026-07-09 15:22 ` Sebastian Andrzej Siewior
2026-07-09 16:02 ` Clark Williams
2026-07-10 7:02 ` Sebastian Andrzej Siewior
2026-07-10 7:05 ` Tomas Glozar
2026-07-10 7:23 ` Florian Bezdeka
2026-07-10 15:51 ` Steven Rostedt
2026-07-10 15:57 ` Sebastian Andrzej Siewior
2026-07-10 16:01 ` Florian Bezdeka [this message]
2026-07-10 16:12 ` Steven Rostedt
2026-07-14 11:07 ` Sebastian Andrzej Siewior
2026-07-10 16:05 ` Greg Kroah-Hartman
2026-07-10 16:14 ` Steven Rostedt
2026-07-09 15:54 ` Steven Rostedt
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=ae96c274f166301aba762d97caccddf176ad7968.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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 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.