public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	op-tee@lists.trustedfirmware.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] OP-TEE use UUID API for v5.10
Date: Tue, 13 Oct 2020 08:36:12 +0200	[thread overview]
Message-ID: <20201013063612.GA3325842@jade> (raw)

Hello arm-soc maintainers,

Please pull this small patch which allows to hide uuit_t internals from
the OP-TEE driver.

I know it's a bit late for v5.10, if it's too late please queue it for
v5.11 instead.

Thanks,
Jens

The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:

  Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)

are available in the Git repository at:

  git://git.linaro.org:/people/jens.wiklander/linux-tee.git tags/optee-use-uuid-api-for-v5.10

for you to fetch changes up to 57222a1be27e06ecb81cc2f945e897814d5f461c:

  tee: optee: Use UUID API for exporting the UUID (2020-10-13 08:03:18 +0200)

----------------------------------------------------------------
Use UUID API to export the UUID

Uses export_uuid() to export and uuid_t to an u8 array instead of depending
on the internals of uuid_t.

----------------------------------------------------------------
Andy Shevchenko (1):
      tee: optee: Use UUID API for exporting the UUID

 drivers/tee/optee/device.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-10-13  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  6:36 Jens Wiklander [this message]
2020-10-26 14:38 ` [GIT PULL] OP-TEE use UUID API for v5.10 Arnd Bergmann

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=20201013063612.GA3325842@jade \
    --to=jens.wiklander@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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