From: Suman Anna <s-anna@ti.com>
To: "Andrew F. Davis" <afd@ti.com>, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-remoteproc@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] rpmsg: add THIS_MODULE to rpmsg_driver in rpmsg core
Date: Wed, 4 May 2016 13:56:18 -0500 [thread overview]
Message-ID: <572A45D2.30305@ti.com> (raw)
In-Reply-To: <1462386855-17381-1-git-send-email-afd@ti.com>
On 05/04/2016 01:34 PM, Andrew F. Davis wrote:
> Add register_rpmsg_driver helper macro that adds THIS_MODULE to
> rpmsg_driver for the registering driver. We rename and modify
> the existing register_rpmsg_driver to enable this.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
With the multi-trace comment from patch 3 squashed here properly,
Acked-by: Suman Anna <s-anna@ti.com>
> ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 8 +++++---
> include/linux/rpmsg.h | 8 +++++++-
> 2 files changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
> index 1fcd27c..fe03b2a 100644
> --- a/drivers/rpmsg/virtio_rpmsg_bus.c
> +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
> @@ -436,17 +436,19 @@ static struct bus_type rpmsg_bus = {
> };
>
> /**
> - * register_rpmsg_driver() - register an rpmsg driver with the rpmsg bus
> + * __register_rpmsg_driver() - register an rpmsg driver with the rpmsg bus
> * @rpdrv: pointer to a struct rpmsg_driver
> + * @owner: owning module/driver
> *
> * Returns 0 on success, and an appropriate error value on failure.
> */
> -int register_rpmsg_driver(struct rpmsg_driver *rpdrv)
> +int __register_rpmsg_driver(struct rpmsg_driver *rpdrv, struct module *owner)
> {
> rpdrv->drv.bus = &rpmsg_bus;
> + rpdrv->drv.owner = owner;
> return driver_register(&rpdrv->drv);
> }
> -EXPORT_SYMBOL(register_rpmsg_driver);
> +EXPORT_SYMBOL(__register_rpmsg_driver);
>
> /**
> * unregister_rpmsg_driver() - unregister an rpmsg driver from the rpmsg bus
> diff --git a/include/linux/rpmsg.h b/include/linux/rpmsg.h
> index 82a6739..78e45ce 100644
> --- a/include/linux/rpmsg.h
> +++ b/include/linux/rpmsg.h
> @@ -169,7 +169,7 @@ struct rpmsg_driver {
>
> int register_rpmsg_device(struct rpmsg_channel *dev);
> void unregister_rpmsg_device(struct rpmsg_channel *dev);
> -int register_rpmsg_driver(struct rpmsg_driver *drv);
> +int __register_rpmsg_driver(struct rpmsg_driver *drv, struct module *owner);
> void unregister_rpmsg_driver(struct rpmsg_driver *drv);
> void rpmsg_destroy_ept(struct rpmsg_endpoint *);
> struct rpmsg_endpoint *rpmsg_create_ept(struct rpmsg_channel *,
> @@ -177,6 +177,12 @@ struct rpmsg_endpoint *rpmsg_create_ept(struct rpmsg_channel *,
> int
> rpmsg_send_offchannel_raw(struct rpmsg_channel *, u32, u32, void *, int, bool);
>
> +/*
> + * use a macro to avoid include chaining to get THIS_MODULE
> + */
> +#define register_rpmsg_driver(drv) \
> + __register_rpmsg_driver(drv, THIS_MODULE)
> +
> /**
> * rpmsg_send() - send a message across to the remote processor
> * @rpdev: the rpmsg channel
>
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com>
To: "Andrew F. Davis" <afd@ti.com>, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: <linux-remoteproc@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] rpmsg: add THIS_MODULE to rpmsg_driver in rpmsg core
Date: Wed, 4 May 2016 13:56:18 -0500 [thread overview]
Message-ID: <572A45D2.30305@ti.com> (raw)
In-Reply-To: <1462386855-17381-1-git-send-email-afd@ti.com>
On 05/04/2016 01:34 PM, Andrew F. Davis wrote:
> Add register_rpmsg_driver helper macro that adds THIS_MODULE to
> rpmsg_driver for the registering driver. We rename and modify
> the existing register_rpmsg_driver to enable this.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
With the multi-trace comment from patch 3 squashed here properly,
Acked-by: Suman Anna <s-anna@ti.com>
> ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 8 +++++---
> include/linux/rpmsg.h | 8 +++++++-
> 2 files changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
> index 1fcd27c..fe03b2a 100644
> --- a/drivers/rpmsg/virtio_rpmsg_bus.c
> +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
> @@ -436,17 +436,19 @@ static struct bus_type rpmsg_bus = {
> };
>
> /**
> - * register_rpmsg_driver() - register an rpmsg driver with the rpmsg bus
> + * __register_rpmsg_driver() - register an rpmsg driver with the rpmsg bus
> * @rpdrv: pointer to a struct rpmsg_driver
> + * @owner: owning module/driver
> *
> * Returns 0 on success, and an appropriate error value on failure.
> */
> -int register_rpmsg_driver(struct rpmsg_driver *rpdrv)
> +int __register_rpmsg_driver(struct rpmsg_driver *rpdrv, struct module *owner)
> {
> rpdrv->drv.bus = &rpmsg_bus;
> + rpdrv->drv.owner = owner;
> return driver_register(&rpdrv->drv);
> }
> -EXPORT_SYMBOL(register_rpmsg_driver);
> +EXPORT_SYMBOL(__register_rpmsg_driver);
>
> /**
> * unregister_rpmsg_driver() - unregister an rpmsg driver from the rpmsg bus
> diff --git a/include/linux/rpmsg.h b/include/linux/rpmsg.h
> index 82a6739..78e45ce 100644
> --- a/include/linux/rpmsg.h
> +++ b/include/linux/rpmsg.h
> @@ -169,7 +169,7 @@ struct rpmsg_driver {
>
> int register_rpmsg_device(struct rpmsg_channel *dev);
> void unregister_rpmsg_device(struct rpmsg_channel *dev);
> -int register_rpmsg_driver(struct rpmsg_driver *drv);
> +int __register_rpmsg_driver(struct rpmsg_driver *drv, struct module *owner);
> void unregister_rpmsg_driver(struct rpmsg_driver *drv);
> void rpmsg_destroy_ept(struct rpmsg_endpoint *);
> struct rpmsg_endpoint *rpmsg_create_ept(struct rpmsg_channel *,
> @@ -177,6 +177,12 @@ struct rpmsg_endpoint *rpmsg_create_ept(struct rpmsg_channel *,
> int
> rpmsg_send_offchannel_raw(struct rpmsg_channel *, u32, u32, void *, int, bool);
>
> +/*
> + * use a macro to avoid include chaining to get THIS_MODULE
> + */
> +#define register_rpmsg_driver(drv) \
> + __register_rpmsg_driver(drv, THIS_MODULE)
> +
> /**
> * rpmsg_send() - send a message across to the remote processor
> * @rpdev: the rpmsg channel
>
next prev parent reply other threads:[~2016-05-04 18:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 18:34 [PATCH 1/4] rpmsg: add THIS_MODULE to rpmsg_driver in rpmsg core Andrew F. Davis
2016-05-04 18:34 ` Andrew F. Davis
2016-05-04 18:34 ` [PATCH 2/4] rpmsg: drop owner assignment from spi_drivers Andrew F. Davis
2016-05-04 18:34 ` Andrew F. Davis
2016-05-04 18:55 ` Suman Anna
2016-05-04 18:55 ` Suman Anna
2016-05-04 18:57 ` Andrew F. Davis
2016-05-04 18:57 ` Andrew F. Davis
2016-05-04 18:34 ` [PATCH 3/4] rpmsg: add helper macro module_rpmsg_driver Andrew F. Davis
2016-05-04 18:34 ` Andrew F. Davis
2016-05-04 18:54 ` Suman Anna
2016-05-04 18:54 ` Suman Anna
2016-05-04 18:58 ` Andrew F. Davis
2016-05-04 18:58 ` Andrew F. Davis
2016-05-04 18:34 ` [PATCH 4/4] rpmsg: use module_rpmsg_driver in existing drivers and examples Andrew F. Davis
2016-05-04 18:34 ` Andrew F. Davis
2016-05-04 18:56 ` Suman Anna [this message]
2016-05-04 18:56 ` [PATCH 1/4] rpmsg: add THIS_MODULE to rpmsg_driver in rpmsg core 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=572A45D2.30305@ti.com \
--to=s-anna@ti.com \
--cc=afd@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.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.