linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: ohad@wizery.com, arnaud.pouliquen@st.com, s-anna@ti.com,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] rpmsg: core: Add support for name extension
Date: Fri, 15 May 2020 14:09:14 -0700	[thread overview]
Message-ID: <20200515210914.GA408178@builder.lan> (raw)
In-Reply-To: <20200515205642.13529-1-mathieu.poirier@linaro.org>

On Fri 15 May 13:56 PDT 2020, Mathieu Poirier wrote:

> This patchset adds the capability to supplement the base definition
> published by an rpmsg_driver with a postfix description so that it
> is easy to differentiate entities that use the same name service.
> 
> Applies cleanly on rpmsg-next (4f05fc33bebd).
> 

Thanks Mathieu, this series does look good.


But before merging this, can someone show me a real example where this
is being/would be used? What are some real channel names and extensions?

Regards,
Bjorn

> New for V6:
> - Added example on how to use the new API.
> 
> Thanks,
> Mathieu
> 
> 
> Mathieu Poirier (3):
>   rpmsg: core: Add wildcard match for name service
>   rpmsg: core: Add support to retrieve name extension
>   sample/rpmsg: Print out RPMSG device name extension
> 
>  drivers/rpmsg/rpmsg_core.c          | 115 +++++++++++++++++++++++++++-
>  include/linux/rpmsg.h               |  13 ++++
>  samples/rpmsg/rpmsg_client_sample.c |   5 ++
>  3 files changed, 132 insertions(+), 1 deletion(-)
> 
> -- 
> 2.20.1
> 

  parent reply	other threads:[~2020-05-15 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 20:56 [PATCH v6 0/3] rpmsg: core: Add support for name extension Mathieu Poirier
2020-05-15 20:56 ` [PATCH v6 1/3] rpmsg: core: Add wildcard match for name service Mathieu Poirier
2020-06-08 21:11   ` Suman Anna
2020-05-15 20:56 ` [PATCH v6 2/3] rpmsg: core: Add support to retrieve name extension Mathieu Poirier
2020-06-08 22:47   ` Suman Anna
2020-05-15 20:56 ` [PATCH v6 3/3] sample: rpmsg: Print out RPMSG device " Mathieu Poirier
2020-05-15 21:09 ` Bjorn Andersson [this message]
2020-05-20 14:49   ` [PATCH v6 0/3] rpmsg: core: Add support for " Arnaud POULIQUEN
2020-06-08 22:33     ` Suman Anna

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=20200515210914.GA408178@builder.lan \
    --to=bjorn.andersson@linaro.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=ohad@wizery.com \
    --cc=s-anna@ti.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;
as well as URLs for NNTP newsgroup(s).