From: James Morris <jmorris@namei.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch,
robdclark@gmail.com, treding@nvidia.com, sumit.semwal@linaro.org,
tom.cooksey@arm.com, daniel.stone@collabora.com,
linux-security-module@vger.kernel.org,
xiaoquan.li@vivantecorp.com, labbott@redhat.com,
tom.gall@linaro.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v5 0/3] RFC: Secure Memory Allocation Framework
Date: Thu, 22 Oct 2015 01:34:09 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1510220132490.6421@namei.org> (raw)
In-Reply-To: <1445419340-11471-1-git-send-email-benjamin.gaignard@linaro.org>
On Wed, 21 Oct 2015, Benjamin Gaignard wrote:
>
> The outcome of the previous RFC about how do secure data path was the need
> of a secure memory allocator (https://lkml.org/lkml/2015/5/5/551)
>
Have you addressed all the questions raised by Alan here:
https://lkml.org/lkml/2015/5/8/629
Also, is there any application of this beyond DRM?
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2015-10-21 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 9:22 Benjamin Gaignard
2015-10-21 9:22 ` [PATCH v5 1/3] create SMAF module Benjamin Gaignard
2015-10-21 14:32 ` James Morris
2015-10-21 15:34 ` Benjamin Gaignard
2015-10-21 9:22 ` [PATCH v5 2/3] SMAF: add CMA allocator Benjamin Gaignard
2015-10-21 9:22 ` [PATCH v5 3/3] SMAF: add fake secure module Benjamin Gaignard
2015-10-21 14:34 ` James Morris [this message]
2015-10-21 15:58 ` [PATCH v5 0/3] RFC: Secure Memory Allocation Framework Benjamin Gaignard
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=alpine.LRH.2.20.1510220132490.6421@namei.org \
--to=jmorris@namei.org \
--cc=benjamin.gaignard@linaro.org \
--cc=daniel.stone@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=tom.cooksey@arm.com \
--cc=tom.gall@linaro.org \
--cc=treding@nvidia.com \
--cc=xiaoquan.li@vivantecorp.com \
/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
all inboxes | Powered by JetHome®