From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
Cc: kvm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
virtualization@lists.linux-foundation.org,
sound-open-firmware@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v2 4/5] rpmsg: update documentation
Date: Mon, 25 May 2020 14:10:35 -0600 [thread overview]
Message-ID: <20200525201035.GB9309@xps15> (raw)
In-Reply-To: <20200525144458.8413-5-guennadi.liakhovetski@linux.intel.com>
On Mon, May 25, 2020 at 04:44:57PM +0200, Guennadi Liakhovetski wrote:
> rpmsg_create_ept() takes struct rpmsg_channel_info chinfo as its last
> argument, not a u32 value.
>
> Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
> ---
> Documentation/rpmsg.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/rpmsg.txt b/Documentation/rpmsg.txt
> index 24b7a9e..4f9bc4f 100644
> --- a/Documentation/rpmsg.txt
> +++ b/Documentation/rpmsg.txt
> @@ -194,7 +194,7 @@ Returns 0 on success and an appropriate error value on failure.
>
> struct rpmsg_endpoint *rpmsg_create_ept(struct rpmsg_channel *rpdev,
> void (*cb)(struct rpmsg_channel *, void *, int, void *, u32),
> - void *priv, u32 addr);
> + void *priv, struct rpmsg_channel_info chinfo);
The second argument, i.e *cb is also wrong. The first argument to the function
pointer is a struct rpmsg_device rather than a rpmsg_channel. Please fix that
while at it by simply using "rpmsg_rx_cb_t cb", the same way it is in
linux/rpmsg.h.
Thanks,
Mathieu
>
> every rpmsg address in the system is bound to an rx callback (so when
> inbound messages arrive, they are dispatched by the rpmsg bus using the
> --
> 1.9.3
>
next prev parent reply other threads:[~2020-05-25 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 14:44 [PATCH v2 0/5] Add a vhost RPMsg API Guennadi Liakhovetski
2020-05-25 14:44 ` [PATCH v2 1/5] vhost: convert VHOST_VSOCK_SET_RUNNING to a generic ioctl Guennadi Liakhovetski
2020-05-25 14:44 ` [PATCH v2 2/5] vhost: (cosmetic) remove a superfluous variable initialisation Guennadi Liakhovetski
2020-05-25 14:44 ` [PATCH v2 3/5] rpmsg: move common structures and defines to headers Guennadi Liakhovetski
2020-05-25 20:06 ` Mathieu Poirier
2020-05-25 14:44 ` [PATCH v2 4/5] rpmsg: update documentation Guennadi Liakhovetski
2020-05-25 20:10 ` Mathieu Poirier [this message]
2020-05-25 14:44 ` [PATCH v2 5/5] vhost: add an RPMsg API Guennadi Liakhovetski
2020-05-25 20:53 ` Mathieu Poirier
2020-05-26 20:50 ` Mathieu Poirier
2020-05-27 17:47 ` Guennadi Liakhovetski
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=20200525201035.GB9309@xps15 \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ohad@wizery.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=virtualization@lists.linux-foundation.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