From: patchwork-bot+linux-remoteproc@kernel.org
To: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v4 0/2] remoteproc: stm32: add support of detaching a remote processor
Date: Wed, 14 Apr 2021 15:10:08 +0000 [thread overview]
Message-ID: <161841300893.3600.15987548617054431266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210331073347.8293-1-arnaud.pouliquen@foss.st.com>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next):
On Wed, 31 Mar 2021 09:33:45 +0200 you wrote:
> Update from V3:
> add Reviewed by Rob Herring in patch 1/2 for bindings
>
> This patchset is the stm32mp1 platform implementation of the detach operation
> added in series [1].
>
> On detach, the stm32 rproc driver sends a mailbox signal to the remote
> processor to inform it that it will be detached.
>
> [...]
Here is the summary with links:
- [v4,1/2] dt-bindings: remoteproc: stm32-rproc: add new mailbox channel for detach
https://git.kernel.org/andersson/remoteproc/c/aca8f94e5b69
- [v4,2/2] remoteproc: stm32: add capability to detach
https://git.kernel.org/andersson/remoteproc/c/edf696f26855
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-14 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 7:33 [PATCH v4 0/2] remoteproc: stm32: add support of detaching a remote processor Arnaud Pouliquen
2021-03-31 7:33 ` [PATCH v4 1/2] dt-bindings: remoteproc: stm32-rproc: add new mailbox channel for detach Arnaud Pouliquen
2021-03-31 7:33 ` [PATCH v4 2/2] remoteproc: stm32: add capability to detach Arnaud Pouliquen
2021-04-13 21:34 ` Bjorn Andersson
2021-04-14 7:23 ` Arnaud POULIQUEN
2021-04-14 15:01 ` Bjorn Andersson
2021-04-14 15:10 ` 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=161841300893.3600.15987548617054431266.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=arnaud.pouliquen@foss.st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).