From: Greg KH <greg@kroah.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
stable@vger.kernel.org, platform-driver-x86@vger.kernel.org,
Artem X <artem.brz@gmail.com>,
Rene Bolldorf <xsecute@googlemail.com>,
Matthew Garrett <mjg@redhat.com>,
Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [PATCH linux-3.1.y] ideapad: Check if acpi already handle backlight power to avoid a page fault
Date: Wed, 11 Jan 2012 08:11:10 -0800 [thread overview]
Message-ID: <20120111161110.GC25593@kroah.com> (raw)
In-Reply-To: <4F0D76D5.2080704@canonical.com>
On Wed, Jan 11, 2012 at 07:47:33PM +0800, Ike Panhc wrote:
> Thanks, and this is necessary for 3.1.y
>
> On 01/11/2012 08:42 AM, Jonathan Nieder wrote:
> > From: René Bollford <xsecute@googlemail.com>
> > Date: Sun, 23 Oct 2011 09:56:42 +0200
> >
> > commit d4afc7754a60b885b63ef23fd194984e2d53a4e6 upstream.
> >
> > This patch avoid a page fault in the ideapad-laptop extras when
> > turning the backlight power on or off.
> >
> > Signed-off-by: Rene Bolldorf <xsecute@googlemail.com>
> > Signed-off-by: Matthew Garrett <mjg@redhat.com>
> > Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> > Tested-by: Artem X <artem.brz@gmail.com>
>
> Acked-by: Ike Panhc <ike.pan@canonical.com>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2012-01-11 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFVLVSOp750X4L+qgR16Qc53V+jOKsxA-ujskx3K0BX9kQOzTw@mail.gmail.com>
2012-01-11 0:42 ` [PATCH linux-3.1.y] ideapad: Check if acpi already handle backlight power to avoid a page fault Jonathan Nieder
2012-01-11 0:56 ` Jonathan Nieder
2012-01-11 11:47 ` Ike Panhc
2012-01-11 16:11 ` Greg KH [this message]
2012-01-11 16:40 ` Jonathan Nieder
2012-01-11 17:05 ` Greg KH
2012-01-11 18:57 ` Jonathan Nieder
2012-01-12 22:59 ` Greg KH
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=20120111161110.GC25593@kroah.com \
--to=greg@kroah.com \
--cc=artem.brz@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=ike.pan@canonical.com \
--cc=jrnieder@gmail.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xsecute@googlemail.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 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.