From: patchwork-bot+linux-remoteproc@kernel.org
To: Sibi Sankar <sibis@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] remoteproc: qcom_q6v5_mss: map/unmap mpss segments before/after use
Date: Wed, 13 May 2020 06:20:06 +0000 [thread overview]
Message-ID: <158935080633.26945.9821739841419532784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200415071619.6052-1-sibis@codeaurora.org>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next).
On Wed, 15 Apr 2020 12:46:18 +0530 you wrote:
> The application processor accessing the mpss region when the Q6 modem is
> running will lead to an XPU violation. Fix this by un-mapping the mpss
> segments post copy during mpss authentication and coredumps.
>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
>
> [...]
Here is a summary with links:
- [v2,1/2] remoteproc: qcom_q6v5_mss: map/unmap mpss segments before/after use
https://git.kernel.org/andersson/remoteproc/c/be050a3429f46ecf13eb2b80f299479f8bb823fb
- [v2,2/2] remoteproc: qcom_q6v5_mss: Remove unused q6v5_da_to_va function
https://git.kernel.org/andersson/remoteproc/c/9666174a4e1a7b1e32c214312678f8452275da6a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
prev parent reply other threads:[~2020-05-13 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 7:16 [PATCH v2 1/2] remoteproc: qcom_q6v5_mss: map/unmap mpss segments before/after use Sibi Sankar
2020-04-15 7:16 ` Sibi Sankar
2020-04-15 7:16 ` [PATCH v2 2/2] remoteproc: qcom_q6v5_mss: Remove unused q6v5_da_to_va function Sibi Sankar
2020-04-15 7:16 ` Sibi Sankar
2020-04-20 18:53 ` Evan Green
2020-04-20 18:53 ` Evan Green
2020-04-20 18:57 ` Evan Green
2020-04-20 18:57 ` Evan Green
2020-04-29 17:27 ` Evan Green
2020-05-13 6:20 ` patchwork-bot+linux-remoteproc [this message]
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=158935080633.26945.9821739841419532784.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sibis@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox