From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: gpio_keys - swtich to dev_pm_ops
Date: Wed, 22 Jul 2009 09:41:16 -0700 [thread overview]
Message-ID: <20090722164116.GC2775@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4A65E58B.6010406@compulab.co.il>
On Tue, Jul 21, 2009 at 06:58:03PM +0300, Mike Rapoport wrote:
>
>
> Dmitry Torokhov wrote:
> > Hi Mike,
> >
> > On Tue, Jul 21, 2009 at 04:59:10PM +0300, Mike Rapoport wrote:
> >> +
> >> +static struct dev_pm_ops gpio_keys_pm_ops = {
> >> + .suspend = gpio_keys_suspend,
> >> + .resume = gpio_keys_resume,
> >> +};
> >>
> >
> > This is not 100% equivalent conversion since we are now only handling
> > s2r, not s2d.. My question though is whether we care or not...
>
> I doubt that systems that use gpio-keys ever supported s2d...
> If you apply it we'll know soon :)
>
> >> static struct platform_driver gpio_keys_device_driver = {
> >> .probe = gpio_keys_probe,
> >> - .remove = __devexit_p(gpio_keys_remove),
> >> - .suspend = gpio_keys_suspend,
> >> .resume = gpio_keys_resume,
I don't think you tried compiling this patch ;( We still need the
remove() method and I think we should keep the CONFIG_PM guards.
I will fix locally.
--
Dmitry
next prev parent reply other threads:[~2009-07-22 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 13:59 [PATCH] Input: gpio_keys - swtich to dev_pm_ops Mike Rapoport
2009-07-21 15:48 ` Dmitry Torokhov
2009-07-21 15:58 ` Mike Rapoport
2009-07-22 16:41 ` Dmitry Torokhov [this message]
2009-07-26 5:57 ` Mike Rapoport
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=20090722164116.GC2775@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mike@compulab.co.il \
/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).