All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<arnaud.pouliquen@st.com>
Subject: [PATCH v2 1/8] rpmsg: virtio: rename rpmsg_create_channel
Date: Tue, 25 Aug 2020 18:49:00 +0200	[thread overview]
Message-ID: <20200825164907.3642-2-arnaud.pouliquen@st.com> (raw)
In-Reply-To: <20200825164907.3642-1-arnaud.pouliquen@st.com>

Rename the internal function as it is internal, and as
the name will be used in rpmsg_core.

Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
---
 drivers/rpmsg/virtio_rpmsg_bus.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
index 9006fc7f73d0..736bc7b9dea8 100644
--- a/drivers/rpmsg/virtio_rpmsg_bus.c
+++ b/drivers/rpmsg/virtio_rpmsg_bus.c
@@ -390,8 +390,9 @@ static void virtio_rpmsg_release_device(struct device *dev)
  * this function will be used to create both static and dynamic
  * channels.
  */
-static struct rpmsg_device *rpmsg_create_channel(struct virtproc_info *vrp,
-						 struct rpmsg_channel_info *chinfo)
+static struct rpmsg_device *
+__rpmsg_create_channel(struct virtproc_info *vrp,
+		       struct rpmsg_channel_info *chinfo)
 {
 	struct virtio_rpmsg_channel *vch;
 	struct rpmsg_device *rpdev;
@@ -864,7 +865,7 @@ static int rpmsg_ns_cb(struct rpmsg_device *rpdev, void *data, int len,
 		if (ret)
 			dev_err(dev, "rpmsg_destroy_channel failed: %d\n", ret);
 	} else {
-		newch = rpmsg_create_channel(vrp, &chinfo);
+		newch = __rpmsg_create_channel(vrp, &chinfo);
 		if (!newch)
 			dev_err(dev, "rpmsg_create_channel failed\n");
 	}
-- 
2.17.1


  reply	other threads:[~2020-08-25 16:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 16:48 [PATCH v2 0/8] introduce name service announcement rpmsg driver Arnaud Pouliquen
2020-08-25 16:49 ` Arnaud Pouliquen [this message]
2020-08-25 16:49 ` [PATCH v2 2/8] rpmsg: core: add channel creation internal API Arnaud Pouliquen
2020-08-25 16:49 ` [PATCH v2 3/8] rpmsg: virtio: add rpmsg channel device ops Arnaud Pouliquen
2020-08-25 16:49 ` [PATCH v2 4/8] rpmsg: define the name service announcement as reserved address Arnaud Pouliquen
2020-08-25 16:49 ` [PATCH v2 5/8] rpmsg: introduce reserved rpmsg driver for ns announcement Arnaud Pouliquen
2020-09-03 23:00   ` Mathieu Poirier
2020-09-04  8:28     ` Arnaud POULIQUEN
2020-09-08 22:03       ` Mathieu Poirier
2020-09-18 23:10   ` Mathieu Poirier
2020-09-21  7:46     ` Arnaud POULIQUEN
2020-08-25 16:49 ` [PATCH v2 6/8] rpmsg: virtio: use rpmsg ns device for the " Arnaud Pouliquen
2020-08-25 16:49 ` [PATCH v2 7/8] rpmsg: ns: add name service announcement service Arnaud Pouliquen
2020-08-25 16:49 ` [PATCH v2 8/8] rpmsg: virtio: use rpmsg_ns driver to manage ns announcement Arnaud Pouliquen

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=20200825164907.3642-2-arnaud.pouliquen@st.com \
    --to=arnaud.pouliquen@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mathieu.poirier@linaro.org \
    --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.