All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: op-tee@lists.trustedfirmware.org
Subject: [GIT PULL] OP-TEE another fix for v5.17
Date: Mon, 14 Feb 2022 13:59:31 +0100	[thread overview]
Message-ID: <20220214125931.GA1332792@jade> (raw)

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

Hello arm-soc maintainers,

Please pull this small OP-TEE driver fix taking care of a broken return
code in the error path of the two probe functions in the OP-TEE driver.

Please note that this pull request is on top of the previously just merged
patch which introduced the problem fixed here.

Thanks,
Jens

The following changes since commit aceeafefff736057e8f93f19bbfbef26abd94604:

  optee: use driver internal tee_context for some rpc (2022-02-03 13:36:32 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 40eb0dcf4114cbfff4d207890fa5a19e82da9fdc:

  tee: optee: fix error return code in probe function (2022-02-14 12:36:48 +0100)

----------------------------------------------------------------
OP-TEE fix error return code in probe functions

----------------------------------------------------------------
Yang Yingliang (1):
      tee: optee: fix error return code in probe function

 drivers/tee/optee/ffa_abi.c | 4 +++-
 drivers/tee/optee/smc_abi.c | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
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,
	Yang Yingliang <yangyingliang@huawei.com>,
	sumit.garg@linaro.org
Subject: [GIT PULL] OP-TEE another fix for v5.17
Date: Mon, 14 Feb 2022 13:59:31 +0100	[thread overview]
Message-ID: <20220214125931.GA1332792@jade> (raw)

Hello arm-soc maintainers,

Please pull this small OP-TEE driver fix taking care of a broken return
code in the error path of the two probe functions in the OP-TEE driver.

Please note that this pull request is on top of the previously just merged
patch which introduced the problem fixed here.

Thanks,
Jens

The following changes since commit aceeafefff736057e8f93f19bbfbef26abd94604:

  optee: use driver internal tee_context for some rpc (2022-02-03 13:36:32 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 40eb0dcf4114cbfff4d207890fa5a19e82da9fdc:

  tee: optee: fix error return code in probe function (2022-02-14 12:36:48 +0100)

----------------------------------------------------------------
OP-TEE fix error return code in probe functions

----------------------------------------------------------------
Yang Yingliang (1):
      tee: optee: fix error return code in probe function

 drivers/tee/optee/ffa_abi.c | 4 +++-
 drivers/tee/optee/smc_abi.c | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

             reply	other threads:[~2022-02-14 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 12:59 Jens Wiklander [this message]
2022-02-14 12:59 ` [GIT PULL] OP-TEE another fix for v5.17 Jens Wiklander
2022-02-18 20:40 ` 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=20220214125931.GA1332792@jade \
    --to=jens.wiklander@linaro.org \
    --cc=op-tee@lists.trustedfirmware.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.