From: Lee Jones <lee.jones@linaro.org>
To: Loic Pallardy <loic.pallardy@st.com>
Cc: bjorn.andersson@linaro.org, ohad@wizery.com,
linux-remoteproc@vger.kernel.org, kernel@stlinux.com
Subject: Re: [PATCH 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation
Date: Tue, 29 Nov 2016 09:20:30 +0000 [thread overview]
Message-ID: <20161129092030.GD2683@dell> (raw)
In-Reply-To: <1480096493-7142-1-git-send-email-loic.pallardy@st.com>
On Fri, 25 Nov 2016, Loic Pallardy wrote:
> Since virtio backend creation, it is no more possible for a firmware to
> register twice a service (on different endpoints). rpmsg_register_device
> function is failing when calling device_add for the second time as second
> device has the same name as first one already register.
> It is because name is based only on service name.
>
> This patch adds destination endpoint to service name to create an
> unique device name.
>
> Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
> ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Isn't this a fix?
If so, please use Fixes: tag. This will ensure Bjorn looks at it
quickly and that it's applied to his -next branch.
We really do not want v4.9 to be an unusable kernel version for us.
> diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
> index 3090b0d..dce880f 100644
> --- a/drivers/rpmsg/virtio_rpmsg_bus.c
> +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
> @@ -405,7 +405,8 @@ static struct rpmsg_device *rpmsg_create_channel(struct virtproc_info *vrp,
> */
> rpdev->announce = rpdev->src != RPMSG_ADDR_ANY;
>
> - strncpy(rpdev->id.name, chinfo->name, RPMSG_NAME_SIZE);
> + snprintf(rpdev->id.name, RPMSG_NAME_SIZE, "%s-%d", chinfo->name,
> + chinfo->dst);
>
> rpdev->dev.parent = &vrp->vdev->dev;
> ret = rpmsg_register_device(rpdev);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-11-29 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 17:54 [PATCH 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation Loic Pallardy
2016-11-29 9:20 ` Lee Jones [this message]
2016-12-02 23:19 ` Bjorn Andersson
2016-12-05 8:32 ` loic pallardy
2016-12-06 17:40 ` Bjorn Andersson
2016-12-07 8:42 ` loic pallardy
2016-12-09 6:00 ` Bjorn Andersson
2016-12-11 20:24 ` loic pallardy
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=20161129092030.GD2683@dell \
--to=lee.jones@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=kernel@stlinux.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox