From: patchwork-bot+linux-soc@kernel.org
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] tee: shared memory updates for v5.18
Date: Fri, 25 Feb 2022 17:21:03 +0000 [thread overview]
Message-ID: <164580966330.15608.1862859581571966604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220218184802.GA968155@jade>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 18 Feb 2022 19:48:02 +0100 you wrote:
> Hello arm-soc maintainers,
>
> Please pull this TEE shared memory cleanup. Some kernel internal APIs are
> replaced with easier to use counter parts. The TEE shared memory pool is
> also simplified.
>
> Note that this pull request includes two patches which are outside the TEE
> subsystem:
> - 231b1fc5da09 ("KEYS: trusted: tee: use tee_shm_register_kernel_buf()")
> - e7ddab084740 ("hwrng: optee-rng: use tee_shm_alloc_kernel_buf()")
> Those patches are reviewed by their maintainer. I've also asked the
> maintainers that normally sends patches upstream for these modules if it's
> OK that I take these patches via my tree. As I got no answer I assume that
> it's OK.
>
> [...]
Here is the summary with links:
- [GIT,PULL] tee: shared memory updates for v5.18
https://git.kernel.org/soc/soc/c/25b67f373b49
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-25 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 18:48 [GIT PULL] tee: shared memory updates for v5.18 Jens Wiklander
2022-02-18 18:48 ` Jens Wiklander
2022-02-25 17:21 ` patchwork-bot+linux-soc [this message]
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=164580966330.15608.1862859581571966604.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=jens.wiklander@linaro.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.