All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	grant.likely@linaro.org, robh+dt@kernel.org,
	linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: [PATCH][v3.16.y-ckt] ACPICA: Add new GPE public interface - acpi_mark_gpe_for_wake.
Date: Thu, 15 Jan 2015 15:19:51 -0500	[thread overview]
Message-ID: <54B820E7.4080406@canonical.com> (raw)

Hello,

Please consider including mainline commit c12f07d and bd9b2f9 in the
next v3.16.y-ckt release.  They
were included in the mainline tree as of v3.17-rc1.  A test kernel has
been built and tested, which was confirmed to resolve:
http://bugs.launchpad.net/bugs/1406767 .

commit c12f07d17c12193256a99e20c9a0f130fb8f7be8
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Jul 23 13:12:16 2014 +0800

    ACPICA: Add new GPE public interface - acpi_mark_gpe_for_wake.


Commit c12f07d does not cherry-pick cleanly in 3.16.y.  However, it will
if commit bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a is cherry picked first:

commit bd9b2f9aff26c185c1f8e0cd08a850ee4ace391a
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jul 14 22:41:41 2014 +0200

    ACPI / scan: No implicit wake notification for buttons

   


Sincerely,
Joseph Salisbury



             reply	other threads:[~2015-01-15 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 20:19 Joseph Salisbury [this message]
     [not found] ` <54B820E7.4080406-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2015-01-16 14:21   ` [PATCH][v3.16.y-ckt] ACPICA: Add new GPE public interface - acpi_mark_gpe_for_wake Luis Henriques
2015-01-16 14:21     ` Luis Henriques
2015-01-16 14:21     ` Luis Henriques

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=54B820E7.4080406@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.