* [GIT PULL] OP-TEE fixes for v7.3
@ 2026-10-02 14:24 Jens Wiklander
2026-10-02 14:59 ` Arnd Bergmann
0 siblings, 1 reply; 5+ messages in thread
From: Jens Wiklander @ 2026-10-02 14:24 UTC (permalink / raw)
To: arm, soc; +Cc: linux-kernel, op-tee
Hello soc maintainers,
Please pull these fixes for the OP-TEE driver in the TEE subsystem.
Thanks,
Jens
The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
Linux 7.2 (2026-08-16 14:32:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jenswi/linux-tee.git tags/optee-fixes-for-v7.3
for you to fetch changes up to 3c0d2f1f431c51a11253f28763be723ac782fd7a:
tee: optee: ffa: support shared memory offsets on large-page kernels (2026-10-02 16:08:05 +0200)
----------------------------------------------------------------
OP-TEE fixes for v7.3
- Register the TEE devices only once fully initialized
- Support FF-A shared memory offsets on large-page kernels
----------------------------------------------------------------
Mahantesh Salimath (1):
tee: optee: ffa: support shared memory offsets on large-page kernels
Shao-Fu Chen (1):
optee: register TEE devices only once fully initialized
drivers/tee/optee/ffa_abi.c | 38 ++++++++++++++++++++++++++------------
drivers/tee/optee/optee_msg.h | 4 ++--
drivers/tee/optee/smc_abi.c | 17 ++++++++---------
3 files changed, 36 insertions(+), 23 deletions(-)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] OP-TEE fixes for v7.3
2026-10-02 14:24 [GIT PULL] OP-TEE fixes for v7.3 Jens Wiklander
@ 2026-10-02 14:59 ` Arnd Bergmann
2026-10-02 19:04 ` Jens Wiklander
0 siblings, 1 reply; 5+ messages in thread
From: Arnd Bergmann @ 2026-10-02 14:59 UTC (permalink / raw)
To: Jens Wiklander, arm, soc; +Cc: linux-kernel, op-tee
On Fri, Oct 2, 2026, at 16:24, Jens Wiklander wrote:
> Hello soc maintainers,
>
> Please pull these fixes for the OP-TEE driver in the TEE subsystem.
>
Hi Jens,
I noticed that the contents of this branch are not in Linux-next.
Is this intentional?
Arnd
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] OP-TEE fixes for v7.3
2026-10-02 14:59 ` Arnd Bergmann
@ 2026-10-02 19:04 ` Jens Wiklander
2026-10-02 21:17 ` Arnd Bergmann
0 siblings, 1 reply; 5+ messages in thread
From: Jens Wiklander @ 2026-10-02 19:04 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: arm, soc, linux-kernel, op-tee
Hi Arnd,
On Fri, Oct 2, 2026 at 4:59 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Fri, Oct 2, 2026, at 16:24, Jens Wiklander wrote:
> > Hello soc maintainers,
> >
> > Please pull these fixes for the OP-TEE driver in the TEE subsystem.
> >
>
> Hi Jens,
>
> I noticed that the contents of this branch are not in Linux-next.
> Is this intentional?
I made a small last-minute change in the commit message for "optee:
register TEE devices only once fully initialized". That's why it may
seem new.
"tee: optee: ffa: support shared memory offsets on large-page kernels"
is brand new.
I thought it was better to send them sooner than to sit on them. Both
are added to my next branch, so I assume they will show on the next
update.
Please let me know if you want me to keep them on linux-next for a
minimum number of days before sending the pull request.
Thanks,
Jens
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] OP-TEE fixes for v7.3
2026-10-02 19:04 ` Jens Wiklander
@ 2026-10-02 21:17 ` Arnd Bergmann
2026-10-03 13:41 ` Jens Wiklander
0 siblings, 1 reply; 5+ messages in thread
From: Arnd Bergmann @ 2026-10-02 21:17 UTC (permalink / raw)
To: Jens Wiklander; +Cc: arm, soc, linux-kernel, op-tee
On Fri, Oct 2, 2026, at 21:04, Jens Wiklander wrote:
> On Fri, Oct 2, 2026 at 4:59 PM Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> On Fri, Oct 2, 2026, at 16:24, Jens Wiklander wrote:
>> > Hello soc maintainers,
>> >
>> > Please pull these fixes for the OP-TEE driver in the TEE subsystem.
>>
>> I noticed that the contents of this branch are not in Linux-next.
>> Is this intentional?
>
> I made a small last-minute change in the commit message for "optee:
> register TEE devices only once fully initialized". That's why it may
> seem new.
>
> "tee: optee: ffa: support shared memory offsets on large-page kernels"
> is brand new.
>
> I thought it was better to send them sooner than to sit on them. Both
> are added to my next branch, so I assume they will show on the next
> update.
>
> Please let me know if you want me to keep them on linux-next for a
> minimum number of days before sending the pull request.
Thanks for the explanation, that makes sense. You need to decide how
confident you are in the contents before you send them, I was just
worried that this had not seen any testing at all because it was
inadvertently left out of linux-next.
If you are ever not sure, just mention that in the pull request message.
Arnd
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [GIT PULL] OP-TEE fixes for v7.3
2026-10-02 21:17 ` Arnd Bergmann
@ 2026-10-03 13:41 ` Jens Wiklander
0 siblings, 0 replies; 5+ messages in thread
From: Jens Wiklander @ 2026-10-03 13:41 UTC (permalink / raw)
To: Arnd Bergmann; +Cc: arm, soc, linux-kernel, op-tee
On Fri, Oct 2, 2026 at 11:17 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Fri, Oct 2, 2026, at 21:04, Jens Wiklander wrote:
> > On Fri, Oct 2, 2026 at 4:59 PM Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> On Fri, Oct 2, 2026, at 16:24, Jens Wiklander wrote:
> >> > Hello soc maintainers,
> >> >
> >> > Please pull these fixes for the OP-TEE driver in the TEE subsystem.
> >>
> >> I noticed that the contents of this branch are not in Linux-next.
> >> Is this intentional?
> >
> > I made a small last-minute change in the commit message for "optee:
> > register TEE devices only once fully initialized". That's why it may
> > seem new.
> >
> > "tee: optee: ffa: support shared memory offsets on large-page kernels"
> > is brand new.
> >
> > I thought it was better to send them sooner than to sit on them. Both
> > are added to my next branch, so I assume they will show on the next
> > update.
> >
> > Please let me know if you want me to keep them on linux-next for a
> > minimum number of days before sending the pull request.
>
> Thanks for the explanation, that makes sense. You need to decide how
> confident you are in the contents before you send them, I was just
> worried that this had not seen any testing at all because it was
> inadvertently left out of linux-next.
>
> If you are ever not sure, just mention that in the pull request message.
Got it, thanks.
/Jens
>
> Arnd
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-10-03 13:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-02 14:24 [GIT PULL] OP-TEE fixes for v7.3 Jens Wiklander
2026-10-02 14:59 ` Arnd Bergmann
2026-10-02 19:04 ` Jens Wiklander
2026-10-02 21:17 ` Arnd Bergmann
2026-10-03 13:41 ` Jens Wiklander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®