From: Guenter Roeck <linux@roeck-us.net>
To: linux-pm@vger.kernel.org
Cc: 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>,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH 0/3] pm: Introduce __pm to mark power management code
Date: Thu, 9 May 2013 10:09:48 -0700 [thread overview]
Message-ID: <1368119391-13837-1-git-send-email-linux@roeck-us.net> (raw)
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.
next reply other threads:[~2013-05-09 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 17:09 Guenter Roeck [this message]
2013-05-09 17:09 ` [PATCH 1/3] pm: Introduce __pm to mark power management functions and data Guenter Roeck
2013-05-09 17:09 ` [PATCH 2/3] hwmon: (tmp102) Convert to use __pm instead of #ifdef CONFIG_PM Guenter Roeck
2013-05-09 17:09 ` [PATCH 3/3] hwmon: (max6639) Convert to use __pm instead of #ifdef CONFIG_PM_SLEEP Guenter Roeck
2013-05-10 10:54 ` [PATCH 0/3] pm: Introduce __pm to mark power management code Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
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
2013-05-09 20:30 ` Guenter Roeck
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=1368119391-13837-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--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=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