linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Power management and ACPI fixes for v4.2-rc8
Date: Fri, 21 Aug 2015 00:14:41 +0200	[thread overview]
Message-ID: <CAJZ5v0hhAE=3oWvfSL4zN5=Qb4-yGyCR+XLtm+CVXH0fKvhuuw@mail.gmail.com> (raw)

Hi Linus,

Please pull from

 git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
 pm+acpi-4.2-rc8

to receive power management and ACPI fixes for v4.2-rc8 (if you
decide to do an -rc8) or for the final v4.2 with top-most commit
b8a1171f71c62cdd049fbc452a095173d32ee5fd

 Merge branches 'acpi-video' and 'cpufreq-fixes'

on top of commit 2c6625cd545bdd66acff14f3394865d43920a5c7

 Linux 4.2-rc7

These fix a recent regression in the ACPI backlight code and a memory
leak in the Exynos cpufreq driver.

Specifics:

 - Fix a recently introduced issue in the ACPI backlight code which
   causes lockdep to complain about a circular lock dependency during
   initialization (Hans de Goede).

 - Fix a possible memory leak during initialization in the Exynos cpufreq
   driver (Shailendra Verma).

Thanks!


---------------

Hans de Goede (1):
      ACPI / video: Fix circular lock dependency issue in the video-detect code

Shailendra Verma (1):
      cpufreq: exynos: Fix for memory leak in case SoC name does not match

---------------

 drivers/acpi/video_detect.c      | 16 +++++++++++++---
 drivers/cpufreq/exynos-cpufreq.c |  6 ++++--
 2 files changed, 17 insertions(+), 5 deletions(-)

                 reply	other threads:[~2015-08-20 22:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJZ5v0hhAE=3oWvfSL4zN5=Qb4-yGyCR+XLtm+CVXH0fKvhuuw@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).