All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrice Chotard <patrice.chotard@st.com>
To: Loic Pallardy <loic.pallardy@st.com>,
	bjorn.andersson@linaro.org, ohad@wizery.com,
	lee.jones@linaro.org
Cc: linux-remoteproc@vger.kernel.org, kernel@stlinux.com
Subject: Re: [PATCH v1 0/3] remoteproc: st: add virtio_rpmsg support
Date: Wed, 4 Jan 2017 08:40:05 +0100	[thread overview]
Message-ID: <a7c1e23b-b77b-533f-75ee-10ee96e885c9@st.com> (raw)
In-Reply-To: <1481142826-15528-1-git-send-email-loic.pallardy@st.com>

On 12/07/2016 09:33 PM, Loic Pallardy wrote:
> Goal of this series is:
> - to add vring based communication link (virtio_rpmsg)
> - to add rproc_da_to_va translation function to allow firmware loading in
>   pre-reserved carveout memory region
> 
> Loic Pallardy (3):
>   remoteproc: st: add virtio communication support
>   remoteproc: st: add da to va support
>   remoteproc: core: don't allocate carveout if pa or da are defined
> 
>  drivers/remoteproc/Kconfig           |   3 +
>  drivers/remoteproc/remoteproc_core.c |   5 ++
>  drivers/remoteproc/st_remoteproc.c   | 161 +++++++++++++++++++++++++++++++++--
>  3 files changed, 163 insertions(+), 6 deletions(-)
> 

Hi Loic

For the entire series

Acked-by: Patrice Chotard <patrice.chotard@st.com>

Patrice

  parent reply	other threads:[~2017-01-04  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 20:33 [PATCH v1 0/3] remoteproc: st: add virtio_rpmsg support Loic Pallardy
2016-12-07 20:33 ` [PATCH v1 1/3] remoteproc: st: add virtio communication support Loic Pallardy
2017-01-18 23:23   ` Bjorn Andersson
2017-01-19 15:29     ` Loic PALLARDY
2016-12-07 20:33 ` [PATCH v1 2/3] remoteproc: st: add da to va support Loic Pallardy
2016-12-07 20:33 ` [PATCH v1 3/3] remoteproc: core: don't allocate carveout if pa or da are defined Loic Pallardy
2017-01-04  7:40 ` Patrice Chotard [this message]
2017-01-06 16:32 ` [STLinux Kernel] [PATCH v1 0/3] remoteproc: st: add virtio_rpmsg support Peter Griffin

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=a7c1e23b-b77b-533f-75ee-10ee96e885c9@st.com \
    --to=patrice.chotard@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --cc=ohad@wizery.com \
    /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.