[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131115020959.GA8644@kroah.com>
Date: Fri, 15 Nov 2013 11:09:59 +0900
From: Greg KH <gregkh@...uxfoundation.org>
To: Shuah Khan <shuah.kh@...sung.com>
Cc: rjw@...ysocki.net, shuahkhan@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Add Legacy PM OPS usage checks to class, bus, and
driver register functions
On Thu, Nov 14, 2013 at 08:43:27AM -0700, 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?
It's the middle of the merge window, where I can't apply any new
patches, and I'm traveling in Korea, so nothing is getting done on any
patches anyone has sent me, you aren't alone :)
Wait until 3.13-rc1 is out, then I'll start digging through my patch
queue and reviewing them, your's is in there as well.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists