From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>Bjorn Andersson
<bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
stable@vger.kernel.orgstable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] remoteproc: qcom_q6v5_mss: Don't reassign mpss region on shutdown
Date: Wed, 05 Feb 2020 14:45:10 +0000 [thread overview]
Message-ID: <20200205144511.ADE722082E@mail.kernel.org> (raw)
In-Reply-To: <20200204062641.393949-2-bjorn.andersson@linaro.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 6c5a9dc2481b ("remoteproc: qcom: Make secure world call for mem ownership switch").
The bot has tested the following trees: v5.5.1, v5.4.17, v4.19.101.
v5.5.1: Build OK!
v5.4.17: Build OK!
v4.19.101: Failed to apply! Possible dependencies:
0304530ddd29 ("remoteproc: qcom: q6v5-mss: Refactor mba load/unload sequence")
7dd8ade24dc2 ("remoteproc: qcom: q6v5-mss: Add custom dump function for modem")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-05 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 6:26 [PATCH v3 0/2] remoteproc: mss: Improve mem_assign and firmware load Bjorn Andersson
2020-02-04 6:26 ` [PATCH v3 1/2] remoteproc: qcom_q6v5_mss: Don't reassign mpss region on shutdown Bjorn Andersson
2020-02-05 14:45 ` Sasha Levin [this message]
2020-02-10 23:05 ` Mathieu Poirier
2020-02-11 1:16 ` Bjorn Andersson
2020-02-11 18:42 ` Mathieu Poirier
2020-02-04 6:26 ` [PATCH v3 2/2] remoteproc: qcom_q6v5_mss: Validate each segment during loading Bjorn Andersson
2020-02-10 23:10 ` Mathieu Poirier
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=20200205144511.ADE722082E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=stable@vger.kernel.orgstable \
/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