public inbox for op-tee@lists.trustedfirmware.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	op-tee@lists.trustedfirmware.org
Subject: [GIT PULL] TEE QTEE fixes for v6.18
Date: Fri, 3 Oct 2025 14:32:49 +0200	[thread overview]
Message-ID: <20251003123249.GA1063437@rayden> (raw)

Hello arm-soc maintainers,

Please pull these small fixes for the TEE QTEE driver introduced in v6.18
merge window.

Thanks,
Jens

The following changes since commit dcc7a571a3665a16581b5b18ca6b113f60a9a41a:

  Documentation: tee: Add Qualcomm TEE driver (2025-09-15 17:34:06 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jenswi/linux-tee.git tags/tee-qcomtee-fixes-for-v6.18

for you to fetch changes up to 3b63efa21bc6acc1a0fadd1dd0f0e1988a4c0177:

  tee: QCOMTEE should depend on ARCH_QCOM (2025-10-02 08:31:10 +0200)

----------------------------------------------------------------
TEE QTEE fixes for v6.18

- Adds ARCH_QCOM dependency for the QTEE driver
- Fixing return values for copy_from_user() failures
- Guarding against potential off by one read

----------------------------------------------------------------
Dan Carpenter (2):
      tee: qcom: prevent potential off by one read
      tee: qcom: return -EFAULT instead of -EINVAL if copy_from_user() fails

Geert Uytterhoeven (1):
      tee: QCOMTEE should depend on ARCH_QCOM

 drivers/tee/qcomtee/Kconfig | 1 +
 drivers/tee/qcomtee/call.c  | 2 +-
 drivers/tee/qcomtee/core.c  | 2 +-
 3 files changed, 3 insertions(+), 2 deletions(-)

                 reply	other threads:[~2025-10-03 12:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251003123249.GA1063437@rayden \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --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