From: Peter Korsgaard <jacmet@sunsite.dk>
To: "Maxin B. John" <maxin.john@gmail.com>
Cc: wsa@the-dreams.de, ben-linux@fluff.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
"Maxin B. John" <maxin.john@enea.com>
Subject: Re: [PATCH] i2c: busses: i2c-ocores: Fix PM-related warning
Date: Mon, 04 Mar 2013 11:01:40 +0100 [thread overview]
Message-ID: <87ppzfcwl7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAMhs6Yy+CFB-dC7PKCEn=19JbiKz=DqWW1G=QeLUzTvwakE_rg@mail.gmail.com> (Maxin B. John's message of "Mon, 4 Mar 2013 10:18:20 +0100")
>>>>> "Maxin" == Maxin B John <maxin.john@gmail.com> writes:
Maxin> On Tue, Feb 26, 2013 at 10:53 PM, <maxin.john@gmail.com> wrote:
>> From: "Maxin B. John" <maxin.john@enea.com>
>>
>> Fixes this warning:
>> CC drivers/i2c/busses/i2c-ocores.o
>> drivers/i2c/busses/i2c-ocores.c:460:12: warning: 'ocores_i2c_suspend'
>> defined but not used [-Wunused-function]
>> drivers/i2c/busses/i2c-ocores.c:471:12: warning: 'ocores_i2c_resume'
>> defined but not used [-Wunused-function]
>>
>> Signed-off-by: Maxin B. John <maxin.john@enea.com>
>> ---
>> drivers/i2c/busses/i2c-ocores.c | 9 +++------
>> 1 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-ocores.c b/drivers/i2c/busses/i2c-ocores.c
>> index 0e1f824..1ecea5e 100644
>> --- a/drivers/i2c/busses/i2c-ocores.c
>> +++ b/drivers/i2c/busses/i2c-ocores.c
>> @@ -456,7 +456,7 @@ static int ocores_i2c_remove(struct platform_device *pdev)
>> return 0;
>> }
>>
>> -#ifdef CONFIG_PM
>> +#ifdef CONFIG_PM_SLEEP
>> static int ocores_i2c_suspend(struct device *dev)
>> {
>> struct ocores_i2c *i2c = dev_get_drvdata(dev);
>> @@ -476,12 +476,9 @@ static int ocores_i2c_resume(struct device *dev)
>>
>> return 0;
>> }
>> +#endif
>>
>> static SIMPLE_DEV_PM_OPS(ocores_i2c_pm, ocores_i2c_suspend,
>> ocores_i2c_resume);
A comment explaining that the suspend/resume callbacks are unused in the
!PM_SLEEP mode would be good.
With this change we waste ~100 bytes on a dummy dev_pm_ops structure,
but OK.
>> -#define OCORES_I2C_PM (&ocores_i2c_pm)
>> -#else
>> -#define OCORES_I2C_PM NULL
>> -#endif
>>
>> static struct platform_driver ocores_i2c_driver = {
>> .probe = ocores_i2c_probe,
>> @@ -490,7 +487,7 @@ static struct platform_driver ocores_i2c_driver = {
>> .owner = THIS_MODULE,
>> .name = "ocores-i2c",
>> .of_match_table = ocores_i2c_match,
>> - .pm = OCORES_I2C_PM,
>> + .pm = &ocores_i2c_pm,
>> },
>> };
>>
>> --
>> 1.7.7
>>
Maxin> ping..
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-03-04 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 21:53 [PATCH] i2c: busses: i2c-ocores: Fix PM-related warning maxin.john
2013-03-04 9:18 ` Maxin B. John
2013-03-04 10:01 ` Peter Korsgaard [this message]
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=87ppzfcwl7.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxin.john@enea.com \
--cc=maxin.john@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=wsa@the-dreams.de \
/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