linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.kh@samsung.com>
To: Jingoo Han <jg1.han@samsung.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: "'Richard Purdie'" <rpurdie@rpsys.net>,
	"'Florian Tobias Schandinat'" <FlorianSchandinat@gmx.de>,
	"'Jean-Christophe PLAGNIOL-VILLARD'" <plagnioj@jcrosoft.com>,
	"'Tomi Valkeinen'" <tomi.valkeinen@ti.com>,
	"'Rafael J. Wysocki'" <rafael.j.wysocki@intel.com>,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"'Shuah Khan'" <shuahkhan@gmail.com>,
	Shuah Khan <shuah.kh@samsung.com>
Subject: Re: [PATCH v2] backlight: Convert from Legacy pm ops to dev_pm_ops
Date: Mon, 20 Jan 2014 08:27:01 -0700	[thread overview]
Message-ID: <52DD4045.4050902@samsung.com> (raw)
In-Reply-To: <001f01cf157f$ca2e8530$5e8b8f90$%han@samsung.com>

On 01/19/2014 06:34 PM, Jingoo Han wrote:
> On Monday, January 20, 2014 12:37 AM, Rafael J. Wysocki wrote:
>> On Wednesday, November 14, 2040 04:27:17 AM 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
>>> 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>
>>
>> Can you please resend the patches that nobody took with CCs to
>> linux-pm@vger.kernel.org?  If the original maintainers don't care, I'll be
>> able to pick those patches up then (if they look good).
>
> I already gave the comment, and am waiting v3 patch.
> However, Shuah Khan did not send the v3 patch yet.
>
> Currently, backlight subsystem patches go through mm-tree
> With my acked-by.
>
> Shuah Khan,
> Will you send the v3 patch? As I said, there is the typo in
> commit message. Please fix it.
>     s/rtc class/backlight class
>

Rafael/Jingoo Han,

I did send the v3 patch with the typo fixed. Here is the link:

http://lkml.indiana.edu/hypermail/linux/kernel/1306.0/00219.html

This is a while back. I will rebase and res-test and send it.

thanks,
-- Shuah

-- 
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@samsung.com | (970) 672-0658

  reply	other threads:[~2014-01-20 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2040-11-14 11:27 [PATCH v2] backlight: Convert from Legacy pm ops to dev_pm_ops Shuah Khan
2013-06-01  4:13 ` Jingoo Han
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 [this message]
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=52DD4045.4050902@samsung.com \
    --to=shuah.kh@samsung.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=jg1.han@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    --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).