mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM mailing list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [GIT PULL] More power management updates for 3.4
Date: Wed, 4 Apr 2012 23:26:47 +0200	[thread overview]
Message-ID: <201204042326.47683.rjw@sisk.pl> (raw)
In-Reply-To: <201204010836.30707.rjw@sisk.pl>

Hi,

On Sunday, April 01, 2012, Rafael J. Wysocki wrote:
> Hi Linus,
> 
> I prepared this on Friday with the hope to send the pull request before the end
> of the merge window, but then I had to go to San Francisco (for the LFCS) and
> missed the opportunity.  That said, this includes fixes mostly (and -stable
> ones for that matter), so I think it's appropriate for the -rc1 time frame too. 
> 
> Please pull additional power management updates for 3.4 since commit
> 735e941caa9a35f933297af0ab1e0ad6447411c4:
> 
>     Merge tag 'common-clk-api' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
> 
> with top-most commit c4772d192c70b61d52262b0db76f7abd8aeb51c6:
> 
>     PM / QoS: add pm_qos_update_request_timeout() API
> 
> from the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-for-3.4-part-2

Given the lack of feedback and the fact that you don't seem to have pulled this,
I wonder if there's anything wrong with the changes or am I simply supposed to
queue them up for 3.5?

Or would you like me to prepare another pull request without the top-most
commit that doesn't count as a fix (I rather won't be able to prepare it
before -rc2 is out, though, due to travel-related limitations)?

Rafael


> This mostly consists of fixes and changes requisite for those fixes, with the
> exception of the last commit, which is a new feature.  However, that new
> feature is reasonably isolated and very unlikely to cause any regressions to
> happen, although it is necessary for some future changes in the works now.
> Included are:
> 
> * Patch series that hopefully fixes races between the freezer and request_firmware()
>   and request_firmware_nowait() for good, with two cleanups from Stephen Boyd on top.
> 
> * Runtime PM fix from Alan Stern preventing tasks from getting stuck indefinitely
>   in the runtime PM wait queue.
> 
> * Device PM QoS update from MyungJoo Ham introducing a new variant of
>   pm_qos_update_request() allowing the callers to specify a timeout.
> 
> Thanks!
> 
> 
>  drivers/base/firmware_class.c |  208 +++++++++++++++++++++--------------------
>  drivers/base/power/runtime.c  |    3 +-
>  include/linux/kmod.h          |   27 +++++-
>  include/linux/pm_qos.h        |    4 +
>  kernel/kmod.c                 |  117 +++++++++++++++++------
>  kernel/power/hibernate.c      |   18 +---
>  kernel/power/process.c        |    8 ++
>  kernel/power/qos.c            |   50 ++++++++++
>  kernel/power/suspend.c        |    7 --
>  kernel/power/user.c           |   10 +--
>  10 files changed, 284 insertions(+), 168 deletions(-)
> 
> ---------------
> 
> Alan Stern (1):
>       PM / Runtime: don't forget to wake up waitqueue on failure
> 
> MyungJoo Ham (1):
>       PM / QoS: add pm_qos_update_request_timeout() API
> 
> Rafael J. Wysocki (6):
>       firmware_class: Rework usermodehelper check
>       firmware_class: Split _request_firmware() into three functions, v2
>       firmware_class: Do not warn that system is not ready from async loads
>       PM / Hibernate: Disable usermode helpers right before freezing tasks
>       PM / Sleep: Move disabling of usermode helpers to the freezer
>       PM / Sleep: Mitigate race between the freezer and request_firmware()
> 
> Stephen Boyd (2):
>       firmware_class: Reorganize fw_create_instance()
>       firmware_class: Move request_firmware_nowait() to workqueues
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


  reply	other threads:[~2012-04-04 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01  6:36 Rafael J. Wysocki
2012-04-04 21:26 ` Rafael J. Wysocki [this message]
2012-04-04 21:29   ` Linus Torvalds
2012-04-04 21:41     ` Rafael J. Wysocki

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=201204042326.47683.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=sboyd@codeaurora.org \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /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

Powered by JetHome