From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Pratyush Brahma <quic_pbrahma@quicinc.com>
Cc: <sumit.semwal@linaro.org>, <benjamin.gaignard@collabora.com>,
<Brian.Starkey@arm.com>, <jstultz@google.com>,
<tjmercier@google.com>, <christian.koenig@amd.com>,
<linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>,
<quic_guptap@quicinc.com>,
Vijayanand Jitta <quic_vjitta@quicinc.com>
Subject: Re: [PATCH 1/2] dma-buf: heaps: secure_heap: Add secure ops for CMA heap
Date: Fri, 24 Nov 2023 13:13:55 +0530 [thread overview]
Message-ID: <a5274efd-cd1b-4ee2-90f4-e0ad88329764@quicinc.com> (raw)
In-Reply-To: <50efb85e259020cf011ba33cffc092e1115b1442.1700544802.git.quic_vjitta@quicinc.com>
Hi Pratyush,
On Wed, Nov 22, 2023 at 07:17:46PM +0530, Pratyush Brahma wrote:
> From: Vijayanand Jitta <quic_vjitta@quicinc.com>
>
> Add secure ops for CMA heap which would use qcom_scm_assign_mem
> to assign the memory to VMID.
>
> Change-Id: I05aff9cb9b7b9668c4352a24bec163b52e38835a
> Signed-off-by: Vijayanand Jitta <quic_vjitta@quicinc.com>
> ---
> drivers/dma-buf/heaps/secure_heap.c | 50 +++++++++++++++++++++++++++--
> 1 file changed, 47 insertions(+), 3 deletions(-)
>
Please add your Signed-off-by line when sending patches. This is a
requirement for accpeting patches in upstream. This applies even for the
patches not authored by you. Given that you are sending the patches,
your Signed-off-by line should be added after Vijay's. For more details
https://docs.kernel.org/process/submitting-patches.html
Thanks,
Pavan
next prev parent reply other threads:[~2023-11-24 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:47 [PATCH 0/2] Add qcom secure heaps Pratyush Brahma
2023-11-22 13:47 ` [PATCH 1/2] dma-buf: heaps: secure_heap: Add secure ops for CMA heap Pratyush Brahma
2023-11-24 7:43 ` Pavan Kondeti [this message]
2023-11-22 13:47 ` [PATCH 2/2] dma-buf: heaps: secure_heap: Add qcom secure system heap Pratyush Brahma
2024-02-20 18:23 ` Elliot Berman
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=a5274efd-cd1b-4ee2-90f4-e0ad88329764@quicinc.com \
--to=quic_pkondeti@quicinc.com \
--cc=Brian.Starkey@arm.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=quic_guptap@quicinc.com \
--cc=quic_pbrahma@quicinc.com \
--cc=quic_vjitta@quicinc.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.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®