From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: tps65010: remove incorrect __exit markups
Date: Mon, 6 Apr 2015 11:24:21 -0700 [thread overview]
Message-ID: <20150406182421.GA36776@dtor-ws> (raw)
In-Reply-To: <20150309174715.GA21698@dtor-ws>
Hi Lee,
On Mon, Mar 09, 2015 at 10:47:15AM -0700, Dmitry Torokhov wrote:
> Even if bus is not hot-pluggable, the devices can be unbound from the
> driver via sysfs, so we should not be using __exit annotations on
> remove() methods. The only exception is drivers registered with
> platform_driver_probe() which specifically disables sysfs bind/unbind
> attributes.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
*ping*
Thanks.
> ---
> drivers/mfd/tps65010.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mfd/tps65010.c b/drivers/mfd/tps65010.c
> index 743fb52..448f0a1 100644
> --- a/drivers/mfd/tps65010.c
> +++ b/drivers/mfd/tps65010.c
> @@ -515,7 +515,7 @@ static int tps65010_gpio_get(struct gpio_chip *chip, unsigned offset)
>
> static struct tps65010 *the_tps;
>
> -static int __exit tps65010_remove(struct i2c_client *client)
> +static int tps65010_remove(struct i2c_client *client)
> {
> struct tps65010 *tps = i2c_get_clientdata(client);
> struct tps65010_board *board = dev_get_platdata(&client->dev);
> @@ -684,7 +684,7 @@ static struct i2c_driver tps65010_driver = {
> .name = "tps65010",
> },
> .probe = tps65010_probe,
> - .remove = __exit_p(tps65010_remove),
> + .remove = tps65010_remove,
> .id_table = tps65010_id,
> };
>
> --
> 2.2.0.rc0.207.ga3a616c
>
>
> --
> Dmitry
--
Dmitry
next prev parent reply other threads:[~2015-04-06 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 17:47 [PATCH] mfd: tps65010: remove incorrect __exit markups Dmitry Torokhov
2015-04-06 18:24 ` Dmitry Torokhov [this message]
2015-04-07 6:55 ` Lee Jones
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=20150406182421.GA36776@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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