From: patchwork-bot+linux-remoteproc@kernel.org
To: Baolin Wang <baolin.wang7@gmail.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] Some improvements for Qualcomm hwspinlock
Date: Wed, 22 Jan 2020 00:40:08 +0000 [thread overview]
Message-ID: <157965360800.2917.12141240213132498058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1578452735.git.baolin.wang7@gmail.com>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next).
On Wed, 8 Jan 2020 11:09:09 +0800 you wrote:
> This patch set did some optimization for Qualcomm hwlock controller,
> including using devm_hwspin_lock_register() API to simplify code and
> removing redundant pm runtime functions.
>
> Baolin Wang (2):
> hwspinlock: qcom: Remove redundant PM runtime functions
> hwspinlock: qcom: Use devm_hwspin_lock_register() to register hwlock
> controller
>
> [...]
Here is a summary with links:
- [RESEND,1/2] hwspinlock: qcom: Remove redundant PM runtime functions
https://git.kernel.org/andersson/remoteproc/c/98ec52ad814013042e0ed386dcfb0c571782e844
- [RESEND,2/2] hwspinlock: qcom: Use devm_hwspin_lock_register() to register hwlock controller
https://git.kernel.org/andersson/remoteproc/c/ed0611a604297a642c3fbec86d3482d580b4f764
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-01-22 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 3:09 [PATCH RESEND 0/2] Some improvements for Qualcomm hwspinlock Baolin Wang
2020-01-08 3:09 ` [PATCH RESEND 1/2] hwspinlock: qcom: Remove redundant PM runtime functions Baolin Wang
2020-01-08 3:09 ` [PATCH RESEND 2/2] hwspinlock: qcom: Use devm_hwspin_lock_register() to register hwlock controller Baolin Wang
2020-01-22 0:15 ` [PATCH RESEND 0/2] Some improvements for Qualcomm hwspinlock Bjorn Andersson
2020-01-22 0:15 ` Bjorn Andersson
2020-01-22 0:40 ` 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=157965360800.2917.12141240213132498058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=baolin.wang7@gmail.com \
--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.