From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "pdurrant@amazon.com" <pdurrant@amazon.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Julien Grall <julien@xen.org>,
"op-tee@lists.trustedfirmware.org"
<op-tee@lists.trustedfirmware.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [PATCH v2 0/2] optee: SHM handling fixes
Date: Fri, 19 Jun 2020 22:33:55 +0000 [thread overview]
Message-ID: <20200619223332.438344-1-volodymyr_babchuk@epam.com> (raw)
There are two patches that previously was mailed separatedly. Both
patches fix issues found during testing the OP-TEE 3.9 release.
Julien and Stefano suggested to include this patches in Xen 4.14
release, because optee support still in the preview state and those
patches provide no new functionality, bugfixes only.
Volodymyr Babchuk (2):
optee: immediately free buffers that are released by OP-TEE
optee: allow plain TMEM buffers with NULL address
xen/arch/arm/tee/optee.c | 59 +++++++++++++++++++++++++++++++++++-----
1 file changed, 52 insertions(+), 7 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-19 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 22:33 Volodymyr Babchuk [this message]
2020-06-19 22:33 ` [PATCH v2 1/2] optee: immediately free buffers that are released by OP-TEE Volodymyr Babchuk
2020-06-23 1:19 ` Stefano Stabellini
2020-06-19 22:34 ` [PATCH v2 2/2] optee: allow plain TMEM buffers with NULL address Volodymyr Babchuk
2020-06-23 1:19 ` Stefano Stabellini
2020-06-23 2:49 ` Volodymyr Babchuk
2020-06-23 13:31 ` Julien Grall
2020-06-23 21:09 ` Stefano Stabellini
2020-06-26 17:54 ` Julien Grall
2020-06-29 7:42 ` Paul Durrant
2020-07-01 10:03 ` Julien Grall
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=20200619223332.438344-1-volodymyr_babchuk@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=julien@xen.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=pdurrant@amazon.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.