From: patchwork-bot+linux-remoteproc@kernel.org
To: Sibi Sankar <sibis@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Improve general readability of MSS on SC7180
Date: Tue, 04 Feb 2020 05:00:04 +0000 [thread overview]
Message-ID: <158079240449.22181.11242000476784871582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200123131236.1078-1-sibis@codeaurora.org>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next).
On Thu, 23 Jan 2020 18:42:34 +0530 you wrote:
> This series aims to improve the general readability of the mss reset
> sequence on SC7180 SoCs. No functional change intended.
>
> v2:
> * Use regmap_read_poll_timeout for halt_nav and halt_axi
> * Redefine CONN_BOX_SPARE_0 to AXI_GATING_VALID_OVERRIDE
> * Update more details about pipeline glitch issue
> * Drop 2,3 patches from v1
>
> [...]
Here is a summary with links:
- [v2,1/2] remoteproc: qcom: q6v5-mss: Use regmap_read_poll_timeout
https://git.kernel.org/andersson/remoteproc/c/01bf3fec38e9188846f6755cd29da515f5852bc5
- [v2,2/2] remoteproc: qcom: q6v5-mss: Improve readability of reset_assert
https://git.kernel.org/andersson/remoteproc/c/600c39b34369e2a1bf78eb67afb99ce550f271cc
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-02-04 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 13:12 [PATCH v2 0/2] Improve general readability of MSS on SC7180 Sibi Sankar
2020-01-23 13:12 ` [PATCH v2 1/2] remoteproc: qcom: q6v5-mss: Use regmap_read_poll_timeout Sibi Sankar
2020-01-23 22:53 ` Evan Green
2020-01-23 13:12 ` [PATCH v2 2/2] remoteproc: qcom: q6v5-mss: Improve readability of reset_assert Sibi Sankar
2020-01-23 22:54 ` Evan Green
2020-02-04 5:00 ` 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=158079240449.22181.11242000476784871582.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