linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Shuah Khan' <shuah.kh@samsung.com>,
	rpurdie@rpsys.net, FlorianSchandinat@gmx.de,
	plagnioj@jcrosoft.com, tomi.valkeinen@ti.com,
	rafael.j.wysocki@intel.com
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuahkhan@gmail.com, Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH v2] backlight: Convert from Legacy pm ops to dev_pm_ops
Date: Sat, 01 Jun 2013 04:13:31 +0000	[thread overview]
Message-ID: <005901ce5e7e$60212c00$20638400$@samsung.com> (raw)
In-Reply-To: <2236505237-3336-1-git-send-email-shuah.kh@samsung.com>

On Wednesday, November 14, 2040 8:27 PM, Shuah Khan wrote:
> 
> Convert drivers/video/backlight/class to use dev_pm_ops for power
> management and remove Legacy PM ops hooks. With this change, rtc class

There is still the typo.

Please fix it. 
 rtc class -> backlight class


> registers suspend/resume callbacks via class->pm (dev_pm_ops) instead of
> Legacy class->suspend/resume. When __device_suspend() runs call-backs,
> it will find class->pm ops for the backlight class.
> 
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> Cc: Shuah Khan <shuahkhan@gmail.com>



  reply	other threads:[~2013-06-01  4:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  3:59 [PATCH v2] backlight: Convert from Legacy pm ops to dev_pm_ops Shuah Khan
2013-06-01  4:13 ` Jingoo Han [this message]
2013-08-09 21:28 ` David Brown
2013-08-09 21:33   ` Shuah Khan
2014-01-19 15:37 ` Rafael J. Wysocki
2014-01-20  1:34   ` Jingoo Han
2014-01-20 15:27     ` Shuah Khan
2014-02-04 17:55       ` Shuah Khan
2014-02-05  0:17         ` Jingoo Han
2014-01-21 15:29   ` Shuah Khan
2014-02-18 22:20 ` [v2] " sebastian.capella

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='005901ce5e7e$60212c00$20638400$@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rpurdie@rpsys.net \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkhan@gmail.com \
    --cc=tomi.valkeinen@ti.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).