From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Pavel Machek <pavel@ucw.cz>, Jingoo Han <jg1.han@samsung.com>,
linux-pm@vger.kernel.org, "'Len Brown'" <len.brown@intel.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] PM: Add pm_ops_ptr() macro
Date: Thu, 30 May 2013 15:54:20 +0200 [thread overview]
Message-ID: <4119506.fLP8mVnrTk@vostro.rjw.lan> (raw)
In-Reply-To: <20130530105644.GA3595@katana>
On Thursday, May 30, 2013 12:56:45 PM Wolfram Sang wrote:
> On Fri, May 03, 2013 at 11:23:11AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > > Add pm_ops_ptr() macro that allows the .pm entry in the driver structures
> > > > to be assigned without having an #define xxx NULL for the case that PM is
> > > > not enabled.
> > > >
> > > > Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> > >
> > > I've queued this up as v3.11 material.
> >
> > > > --- a/drivers/i2c/busses/i2c-s3c2410.c
> > > > +++ b/drivers/i2c/busses/i2c-s3c2410.c
> > > > @@ -1218,7 +1218,6 @@ static int s3c24xx_i2c_resume(struct device *dev)
> > > > }
> > > > #endif
> > > >
> > > > -#ifdef CONFIG_PM
> > > > static const struct dev_pm_ops s3c24xx_i2c_dev_pm_ops = {
> > > > #ifdef CONFIG_PM_SLEEP
> > > > .suspend_noirq = s3c24xx_i2c_suspend_noirq,
> > > > @@ -1226,11 +1225,6 @@ static const struct dev_pm_ops s3c24xx_i2c_dev_pm_ops = {
> > > > #endif
> > > > };
> > > >
> > > > -#define S3C24XX_DEV_PM_OPS (&s3c24xx_i2c_dev_pm_ops)
> > > > -#else
> > > > -#define S3C24XX_DEV_PM_OPS NULL
> > > > -#endif
> > > > -
> > > > /* device driver for platform bus bits */
> >
> > Will not this enlarge .data by sizeof(struct dev_pm_ops)?
>
> Same question here. Is it the preferred way now to use this new macro
> although having the cost of having an empty dev_pm_ops?
No, it isn't, but if someone wants to use it, I don't really care that much.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-05-30 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:09 Jingoo Han
2013-05-02 21:18 ` Rafael J. Wysocki
2013-05-03 9:23 ` Pavel Machek
2013-05-30 10:56 ` Wolfram Sang
2013-05-30 13:54 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-27 2:54 Jingoo Han
2013-04-27 14:40 ` Rafael J. Wysocki
2013-04-29 5:41 ` Jingoo Han
2013-04-29 11:35 ` Rafael J. Wysocki
2013-04-30 0:21 ` Jingoo Han
2013-04-29 12:12 ` Lars-Peter Clausen
2013-04-30 0:54 ` Jingoo Han
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=4119506.fLP8mVnrTk@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=jg1.han@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®