From: Shuah Khan <shuah.kh@samsung.com>
To: gregkh@linuxfoundation.org, rjw@rjwysocki.net
Cc: Shuah Khan <shuah.kh@samsung.com>,
shuahkhan@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Add Legacy PM OPS usage checks to class, bus, and driver register functions
Date: Mon, 6 Jan 2014 13:03:20 -0700 [thread overview]
Message-ID: <cover.1389034060.git.shuah.kh@samsung.com> (raw)
Add Legacy PM OPS usage checks to class, bus, and driver register functions.
If Legacy PM OPS usage is found, print warning message to indicate that the
driver code needs updating to use Dev PM OPS interfaces. This will help serve
as a way to track drivers that still use Legacy PM OPS and fix them.
This patch set adds Legacy PM OPS usage check and warning to bus_register().
__class_register(), and driver_register().
Individual patches in this series are not dependent on each other. The only
reason this is a series is for context and facilitating discussion on the
overall change as opposed individual patches.
Shuah Khan (3):
drivers/bus: Add Legacy PM OPS usage check and warning to
bus_register()
drivers/class: Add Legacy PM OPS usage check and warning to
__class_register()
driver: Add Legacy PM OPS usage check and warning to driver_register()
drivers/base/bus.c | 3 +++
drivers/base/class.c | 4 ++++
drivers/base/driver.c | 4 ++++
3 files changed, 11 insertions(+)
--
1.8.3.2
next reply other threads:[~2014-01-06 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:03 Shuah Khan [this message]
2014-01-06 20:03 ` [PATCH v2 1/3] drivers/bus: Add Legacy PM OPS usage check and warning to bus_register() Shuah Khan
2014-01-06 20:17 ` Greg KH
2014-01-06 20:30 ` Shuah Khan
2014-01-06 21:29 ` Greg KH
2014-01-06 21:44 ` Shuah Khan
2014-01-06 20:03 ` [PATCH v2 2/3] drivers/class: Add Legacy PM OPS usage check and warning to __class_register() Shuah Khan
2014-01-06 20:03 ` [PATCH v2 3/3] driver: Add Legacy PM OPS usage check and warning to driver_register() Shuah Khan
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=cover.1389034060.git.shuah.kh@samsung.com \
--to=shuah.kh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shuahkhan@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).