From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
lm-sensors@lm-sensors.org, Jean Delvare <khali@linux-fr.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH 0/3] pm: Introduce __pm to mark power management code
Date: Thu, 09 May 2013 21:15 +0200 [thread overview]
Message-ID: <1728768.gTkBc2iT1V@vostro.rjw.lan> (raw)
In-Reply-To: <1368119366-8716-1-git-send-email-linux@roeck-us.net>
On Thursday, May 09, 2013 10:09:23 AM Guenter Roeck wrote:
> The following patch series introduces a marker for power management functions
> and data. This this marker, #ifdef CONFIG_PM and #ifdef CONFIG_PM_SLEEP
> can be removed from most of the code. This ensures that the conditional code
> still compiles but is not included in the object file.
>
> As a side effect, drivers declaring struct dev_pm_ops unconditionally
> get a bit smaller if CONFIG_PM_SLEEP is not configured.
>
> The first patch in the series introduces the marker, the following
> two patches introduce the marker in two drivers to demonstrate its use.
>
> The patch series depends on the "PM: Add pm_ops_ptr() macro" patch
> submitted by Jingoo Han.
What about CCing a PM core maintainer?
Please see my reply to Alan Stern for my opinion.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-05-09 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 17:09 Guenter Roeck
2013-05-09 17:38 ` Alan Stern
2013-05-09 17:48 ` Guenter Roeck
2013-05-09 18:31 ` Alan Stern
2013-05-09 19:12 ` Rafael J. Wysocki
2013-05-09 19:15 ` Rafael J. Wysocki [this message]
2013-05-09 20:30 ` Guenter Roeck
2013-05-09 17:09 Guenter Roeck
2013-05-10 10:54 ` Pavel Machek
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=1728768.gTkBc2iT1V@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=jg1.han@samsung.com \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=pavel@ucw.cz \
/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®