From: Ben Hutchings <ben@decadent.org.uk>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Josh Boyer <jwboyer@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3.8.y] drm/i915: add quirk to invert brightness on eMachines e725
Date: Mon, 22 Apr 2013 02:03:31 +0100 [thread overview]
Message-ID: <1366592611.3408.131.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <87obdmpvyo.fsf@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Wed, 2013-04-10 at 12:37 +0300, Jani Nikula wrote:
> On Wed, 10 Apr 2013, Ben Hutchings <ben@decadent.org.uk> wrote:
> > I cherry-picked the following series for Debian:
> >
> > [pre-3.8]
> > 7bd90909bbf9 drm/i915: panel: invert brightness via parameter
> > 4dca20efb1a9 drm/i915: panel: invert brightness via quirk
> > 5a15ab5b93e4 drm/i915: panel: invert brightness acer aspire 5734z
> > 5f85f176c2f1 DRM/i915: Add QUIRK_INVERT_BRIGHTNESS for NCR machines.
> > [post-3.8]
> > 1ffff6032087 drm/i915: add quirk to invert brightness on eMachines G725
> > 01e3a8feb40e drm/i915: add quirk to invert brightness on eMachines e725
> > 5559ecadad5a drm/i915: add quirk to invert brightness on Packard Bell NCL20
> >
> > Should these all be applied to the various 3.x.y stable branches?
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
Queued up for 3.2, thanks.
Ben.
--
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy others.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-04-22 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 12:38 Josh Boyer
2013-04-09 14:12 ` Jani Nikula
2013-04-09 14:22 ` Josh Boyer
2013-04-10 2:34 ` Ben Hutchings
2013-04-10 9:37 ` Jani Nikula
2013-04-22 1:03 ` Ben Hutchings [this message]
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=1366592611.3408.131.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®