From: Jonathan Corbet <corbet@lwn.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-devel@lists.linux.dev, linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
"jenswi@kernel.org" <jenswi@kernel.org>,
op-tee@lists.trustedfirmware.org,
Ard Biesheuvel <ardb@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH v2] Documentation: Extend the real-time hardware bits with some firmware bits
Date: Thu, 13 Aug 2026 09:28:08 -0600 [thread overview]
Message-ID: <87h5kyhwfr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260813082400.h3MRgRPg@linutronix.de>
Sebastian Andrzej Siewior <bigeasy@linutronix.de> writes:
> A gentle ping.
>
> On 2026-07-18 19:50:41 [+0200], To linux-rt-devel@lists.linux.dev wrote:
>> I have been reviewing how OP‑TEE is implemented and how secure‑world
>> invocations behave. The goal was to determine whether an OP‑TEE call can
>> delay the Linux side and introduce latency depending on the time spent
>> in the secure world.
With RT stuff, I never know when something is deemed ready, or whether I
should be the one to pick it up... I have gone ahead and applied this
one, hopefully that was the right thing to do :)
Thanks,
jon
prev parent reply other threads:[~2026-08-13 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 17:50 [PATCH v2] Documentation: Extend the real-time hardware bits with some firmware bits Sebastian Andrzej Siewior
2026-08-13 8:24 ` Sebastian Andrzej Siewior
2026-08-13 15:28 ` Jonathan Corbet [this message]
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=87h5kyhwfr.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=jenswi@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=op-tee@lists.trustedfirmware.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox