mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jens Wiklander" <jens.wiklander@oss.qualcomm.com>
Cc: arm <arm@kernel.org>,
	soc@kernel.org, linux-kernel@vger.kernel.org,
	op-tee@lists.trustedfirmware.org
Subject: Re: [GIT PULL] OP-TEE fixes for v7.3
Date: Fri, 02 Oct 2026 23:17:11 +0200	[thread overview]
Message-ID: <67bbda51-d1b6-45ad-b798-d8c0e53bd23b@app.fastmail.com> (raw)
In-Reply-To: <CAGgiveXqFFi+nq0834+hwBBnwJssh16aayZBgh0toYCVN+OMmA@mail.gmail.com>

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

  reply	other threads:[~2026-10-02 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 14:24 Jens Wiklander
2026-10-02 14:59 ` Arnd Bergmann
2026-10-02 19:04   ` Jens Wiklander
2026-10-02 21:17     ` Arnd Bergmann [this message]
2026-10-03 13:41       ` Jens Wiklander

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=67bbda51-d1b6-45ad-b798-d8c0e53bd23b@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=jens.wiklander@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=soc@kernel.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

all inboxes | Powered by JetHome®