From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
Jingoo Han <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'Len Brown' <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
'Andrew Morton'
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] PM: Add pm_ops_ptr() macro
Date: Thu, 30 May 2013 12:56:45 +0200 [thread overview]
Message-ID: <20130530105644.GA3595@katana> (raw)
In-Reply-To: <20130503092311.GA13832-tWAi6jLit6GreWDznjuHag@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
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-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >
> > 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?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-30 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:09 [PATCH] PM: Add pm_ops_ptr() macro Jingoo Han
2013-05-02 21:18 ` Rafael J. Wysocki
2013-05-03 9:23 ` Pavel Machek
[not found] ` <20130503092311.GA13832-tWAi6jLit6GreWDznjuHag@public.gmane.org>
2013-05-30 10:56 ` Wolfram Sang [this message]
2013-05-30 13:54 ` Rafael J. Wysocki
-- 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=20130530105644.GA3595@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox