All of lore.kernel.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] OP-TEE fixes for v5.17
Date: Wed, 26 Jan 2022 11:26:09 +0100	[thread overview]
Message-ID: <20220126102609.GA1516258@jade> (raw)

Hello arm-soc maintainers,

Please pull these OP-TEE driver fixes all concerning the recent changes
regarding FF-A and asynchronous notifications.

Thanks,
Jens
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.linaro.org/people/jens.wiklander/linux-tee.git tags/optee-fixes-for-v5.17

for you to fetch changes up to 4064c461148ab129dfe5eaeea129b4af6cf4b9b7:

  optee: add error checks in optee_ffa_do_call_with_arg() (2022-01-24 13:00:59 +0100)

----------------------------------------------------------------
OP-TE fixes for v5.17

- Adds error checking in optee_ffa_do_call_with_arg()
- Reintroduces an accidentally lost fix for a memref size check
- Uses bitmap_free() to free memory obtained with bitmap_zalloc()

----------------------------------------------------------------
Christophe JAILLET (1):
      optee: Use bitmap_free() to free bitmap

Jens Wiklander (1):
      optee: add error checks in optee_ffa_do_call_with_arg()

Jerome Forissier (1):
      tee: optee: do not check memref size on return from Secure World

 drivers/tee/optee/ffa_abi.c | 15 ++++++++++++---
 drivers/tee/optee/notif.c   |  2 +-
 drivers/tee/optee/smc_abi.c | 10 ----------
 3 files changed, 13 insertions(+), 14 deletions(-)

             reply	other threads:[~2022-01-26 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 10:26 Jens Wiklander [this message]
2022-02-08  9:12 ` [GIT PULL] OP-TEE fixes for v5.17 patchwork-bot+linux-soc
2022-02-08  9:21 ` patchwork-bot+linux-soc

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=20220126102609.GA1516258@jade \
    --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 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.