From: patchwork-bot+linux-remoteproc@kernel.org
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v7 0/8] rpmsg: Make RPMSG name service modular
Date: Tue, 24 Nov 2020 19:50:07 +0000 [thread overview]
Message-ID: <160624740719.13327.10642451790305903826.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201120214245.172963-1-mathieu.poirier@linaro.org>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next):
On Fri, 20 Nov 2020 14:42:37 -0700 you wrote:
> This revision addresses comments received from the previous revision,
> i.e V6. Please see details below.
>
> It starts by making the RPMSG protocol transport agnostic by
> moving the headers it uses to generic types and using those in the
> current implementation. From there it re-uses the work that Arnaud
> published[1] to make the name service modular.
>
> [...]
Here is the summary with links:
- [v7,1/8] rpmsg: Introduce __rpmsg{16|32|64} types
https://git.kernel.org/andersson/remoteproc/c/6bef038011a0
- [v7,2/8] rpmsg: virtio: Move from virtio to rpmsg byte conversion
https://git.kernel.org/andersson/remoteproc/c/5f2f6b7db119
- [v7,3/8] rpmsg: Move structure rpmsg_ns_msg to header file
https://git.kernel.org/andersson/remoteproc/c/c435a04189de
- [v7,4/8] rpmsg: virtio: Rename rpmsg_create_channel
https://git.kernel.org/andersson/remoteproc/c/77d372989db9
- [v7,5/8] rpmsg: core: Add channel creation internal API
https://git.kernel.org/andersson/remoteproc/c/9753e12cd3bd
- [v7,6/8] rpmsg: virtio: Add rpmsg channel device ops
https://git.kernel.org/andersson/remoteproc/c/1ee1e5e162af
- [v7,7/8] rpmsg: Make rpmsg_{register|unregister}_device() public
https://git.kernel.org/andersson/remoteproc/c/55488110acc1
- [v7,8/8] rpmsg: Turn name service into a stand alone driver
https://git.kernel.org/andersson/remoteproc/c/950a7388f02b
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:[~2020-11-24 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 21:42 [PATCH v7 0/8] rpmsg: Make RPMSG name service modular Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 1/8] rpmsg: Introduce __rpmsg{16|32|64} types Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 2/8] rpmsg: virtio: Move from virtio to rpmsg byte conversion Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 3/8] rpmsg: Move structure rpmsg_ns_msg to header file Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 4/8] rpmsg: virtio: Rename rpmsg_create_channel Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 5/8] rpmsg: core: Add channel creation internal API Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 6/8] rpmsg: virtio: Add rpmsg channel device ops Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 7/8] rpmsg: Make rpmsg_{register|unregister}_device() public Mathieu Poirier
2020-11-20 21:42 ` [PATCH v7 8/8] rpmsg: Turn name service into a stand alone driver Mathieu Poirier
2020-11-23 16:06 ` [PATCH v7 0/8] rpmsg: Make RPMSG name service modular Guennadi Liakhovetski
2020-12-02 11:05 ` Guennadi Liakhovetski
2020-12-02 20:39 ` Mathieu Poirier
2020-12-03 20:42 ` Guennadi Liakhovetski
2020-12-04 17:51 ` Mathieu Poirier
2020-12-07 15:35 ` Kishon Vijay Abraham I
2020-11-24 19:50 ` 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=160624740719.13327.10642451790305903826.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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