From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] as3645a: move .remove under .devexit.text
Date: Mon, 23 Apr 2012 16:51:05 +0300 [thread overview]
Message-ID: <1335189065.18120.187.camel@smile> (raw)
In-Reply-To: <1578696.ouKf8xKIQt@avalon>
On Sat, 2012-04-21 at 19:36 +0200, Laurent Pinchart wrote:
> Hi Andy,
>
> Thanks for the patch.
>
> On Thursday 19 April 2012 16:48:10 Andy Shevchenko wrote:
> > There is no needs to keep .remove under .exit.text. This driver is for a
> > standalone chip that could be on any board and connected to any i2c bus.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> > drivers/media/video/as3645a.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/video/as3645a.c b/drivers/media/video/as3645a.c
> > index 7a3371f..dc2571f 100644
> > --- a/drivers/media/video/as3645a.c
> > +++ b/drivers/media/video/as3645a.c
> > @@ -846,7 +846,7 @@ done:
> > return ret;
> > }
> >
> > -static int __exit as3645a_remove(struct i2c_client *client)
> > +static int __devexit as3645a_remove(struct i2c_client *client)
>
> What about also marking as3645a_probe() with __devinit ?
Yup, we might mark probe() and init_controls() with such tag.
> I might be missing
> something though, as we have very few I2C drivers in drivers/media/video with
> a probe function marked with __devinit (or remove function marked with
> __devexit). Is it time for some cleanup ?
The question is not for me. If I understand correctly that allows not to
keep such code (probe() & related) in the memory after device
initialization. And not use remove() at all in case of CONFIG_MODULE /
CONFIG_HOTPLUG is off.
>
> > {
> > struct v4l2_subdev *subdev = i2c_get_clientdata(client);
> > struct as3645a *flash = to_as3645a(subdev);
> > @@ -877,7 +877,7 @@ static struct i2c_driver as3645a_i2c_driver = {
> > .pm = &as3645a_pm_ops,
> > },
> > .probe = as3645a_probe,
> > - .remove = __exit_p(as3645a_remove),
> > + .remove = __devexit_p(as3645a_remove),
> > .id_table = as3645a_id_table,
> > };
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2012-04-23 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 13:48 [PATCH] as3645a: move .remove under .devexit.text Andy Shevchenko
2012-04-21 17:36 ` Laurent Pinchart
2012-04-23 13:51 ` Andy Shevchenko [this message]
2012-04-23 14:02 ` [PATCHv2] as3645a: move relevant code under __devinit/__devexit Andy Shevchenko
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=1335189065.18120.187.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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.