From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: shuah.kh@samsung.com, shuahkhan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Add Legacy PM OPS usage checks to class, bus, and driver register functions
Date: Tue, 10 Dec 2013 22:53:30 -0800 [thread overview]
Message-ID: <20131211065330.GA25814@kroah.com> (raw)
In-Reply-To: <1786563.y3Kg82Sl7s@vostro.rjw.lan>
On Thu, Nov 14, 2013 at 10:50:29PM +0100, Rafael J. Wysocki wrote:
> On Thursday, November 14, 2013 08:43:27 AM Shuah Khan wrote:
> > On 11/07/2013 05:03 PM, Shuah Khan wrote:
> > > 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 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() functions.
> > >
> > > 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(+)
> > >
> >
> > Greg/Rafael,
> >
> > Any feedback on this series? Haven't gotten to it or don't like it?
>
> I haven't had the time to review this, sorry.
ping?
next prev parent reply other threads:[~2013-12-11 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 0:03 [PATCH 0/3] Add Legacy PM OPS usage checks to class, bus, and driver register functions Shuah Khan
2013-11-08 0:03 ` [PATCH 1/3] drivers/bus: Add Legacy PM OPS usage check and warning to bus_register() Shuah Khan
2013-11-08 0:03 ` [PATCH 2/3] drivers/class: Add Legacy PM OPS usage check and warning to __class_register() Shuah Khan
2013-11-08 0:03 ` [PATCH 3/3] driver: Add Legacy PM OPS usage check and warning to driver_register() Shuah Khan
2013-12-24 0:51 ` Rafael J. Wysocki
2014-01-02 22:59 ` Shuah Khan
2013-11-14 15:43 ` [PATCH 0/3] Add Legacy PM OPS usage checks to class, bus, and driver register functions Shuah Khan
2013-11-14 21:50 ` Rafael J. Wysocki
2013-12-11 6:53 ` Greg KH [this message]
2013-11-15 2:09 ` Greg KH
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=20131211065330.GA25814@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shuah.kh@samsung.com \
--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