From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: rjw@rjwysocki.net, shuahkhan@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] drivers/bus: Add Legacy PM OPS usage check and warning to bus_register()
Date: Mon, 6 Jan 2014 12:17:55 -0800 [thread overview]
Message-ID: <20140106201755.GA7339@kroah.com> (raw)
In-Reply-To: <1b1d24cd7140784f96b9d1fee9cace9da04a88f5.1389034060.git.shuah.kh@samsung.com>
On Mon, Jan 06, 2014 at 01:03:21PM -0700, Shuah Khan wrote:
> Add Legacy PM OPS usage checks to bus_register() function. 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.
>
> The Legacy PM OPS check looks for suspend(struct device *, pm_message_t) or
> resume(struct device *) bus level interfaces.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> ---
> drivers/base/bus.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> index 73f6c29..e8753a7 100644
> --- a/drivers/base/bus.c
> +++ b/drivers/base/bus.c
> @@ -916,6 +916,9 @@ int bus_register(struct bus_type *bus)
> goto bus_groups_fail;
>
> pr_debug("bus: '%s': registered\n", bus->name);
> + if (bus->suspend || bus->resume)
> + pr_warn("bus '%s' needs updating - use pm pointer.\n",
> + bus->name);
Why can't we just sweep the tree for all of these now, fix them up, and
then delete these fields and be done with it?
Same for the other ones, putting warnings in the kernel log files
doesn't work at all for getting people to fix up their code (see
examples of scsi log messages being there for _years_ about obsolete
driver interfaces being used.)
thanks,
greg k-h
next prev parent reply other threads:[~2014-01-06 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:03 [PATCH v2 0/3] Add Legacy PM OPS usage checks to class, bus, and driver register functions Shuah Khan
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 [this message]
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=20140106201755.GA7339@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;
as well as URLs for NNTP newsgroup(s).