From: Stephen Boyd <sboyd@codeaurora.org>
To: "Dwivedi, Avaneesh Kumar (avani)" <akdwived@codeaurora.org>
Cc: bjorn.andersson@linaro.org, agross@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v6 1/4] firmware: scm: Add new SCM call API for switching memory ownership
Date: Thu, 13 Jul 2017 00:54:37 -0700 [thread overview]
Message-ID: <20170713075437.GZ22780@codeaurora.org> (raw)
In-Reply-To: <ef046a1b-4b13-9416-9f28-15f069cc80a8@codeaurora.org>
On 07/13, Dwivedi, Avaneesh Kumar (avani) wrote:
> OK, will do same.
> just last thing to ask, should i resend all 4 patches together again
> or only one patch in v7 version.
> as chnage will be in only 1 out of 4 patches.
I would resend all of them. That's standard practice for patch
series.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-07-13 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 12:08 [PATCH v6 0/4] Add memory ownership switch support and enable mss rproc on msm8996 Avaneesh Kumar Dwivedi
2017-06-22 12:08 ` [PATCH v6 1/4] firmware: scm: Add new SCM call API for switching memory ownership Avaneesh Kumar Dwivedi
2017-07-07 22:49 ` Stephen Boyd
2017-07-10 23:31 ` Bjorn Andersson
2017-07-12 11:03 ` Dwivedi, Avaneesh Kumar (avani)
2017-07-12 19:19 ` Bjorn Andersson
2017-07-13 5:54 ` Stephen Boyd
2017-07-13 7:33 ` Dwivedi, Avaneesh Kumar (avani)
2017-07-13 7:54 ` Stephen Boyd [this message]
2017-07-10 23:43 ` Bjorn Andersson
2017-07-12 11:04 ` Dwivedi, Avaneesh Kumar (avani)
2017-06-22 12:08 ` [PATCH v6 2/4] remoteproc: qcom: refactor mss fw image loading sequence Avaneesh Kumar Dwivedi
2017-06-22 12:08 ` [PATCH v6 3/4] remoteproc: qcom: Make secure world call for mem ownership switch Avaneesh Kumar Dwivedi
2017-06-22 12:08 ` [PATCH v6 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996 Avaneesh Kumar Dwivedi
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=20170713075437.GZ22780@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=akdwived@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.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.