From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] hwmon: max6639: Fix CONFIG_PM compile option
Date: Sat, 24 Mar 2012 19:12:45 +0000 [thread overview]
Message-ID: <20120324191245.GA3251@ericsson.com> (raw)
In-Reply-To: <1332614169-30854-1-git-send-email-stigge@antcom.de>
On Sat, Mar 24, 2012 at 02:36:08PM -0400, Roland Stigge wrote:
> This patch fixes a compiler warning in case CONFIG_PM is not defined
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
> ---
>
> This solves the issue recently encountered by Kurt Roeck in the nightly build.
>
> The solution with #ifdef's is done as in all the other drivers.
>
> drivers/hwmon/max6639.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> --- linux-2.6.orig/drivers/hwmon/max6639.c
> +++ linux-2.6/drivers/hwmon/max6639.c
> @@ -596,6 +596,7 @@ static int max6639_remove(struct i2c_cli
> return 0;
> }
>
> +#ifdef CONFIG_PM
Looking into other drivers, I think that should be CONFIG_PM_SLEEP
> static int max6639_suspend(struct device *dev)
> {
> struct i2c_client *client = to_i2c_client(dev);
> @@ -617,6 +618,10 @@ static int max6639_resume(struct device
> return i2c_smbus_write_byte_data(client,
> MAX6639_REG_GCONFIG, data & ~MAX6639_GCONFIG_STANDBY);
> }
> +#else
> +#define max6639_suspend NULL
> +#define max6639_resume NULL
> +#endif
>
... and that else case should not be necessary.
Oh well, now I ended up looking into it anyway ... so I just added the missing #ifdef to Mark's patch.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-03-24 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 18:36 [lm-sensors] [PATCH] hwmon: max6639: Fix CONFIG_PM compile option Roland Stigge
2012-03-24 19:12 ` Guenter Roeck [this message]
2012-03-24 19:45 ` Roland Stigge
2012-03-24 22:52 ` Guenter Roeck
2012-03-26 10:37 ` Mark Brown
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=20120324191245.GA3251@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=lm-sensors@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.