From: Jani Nikula <jani.nikula@intel.com>
To: Paolo Stivanin <paolostivanin@fastmail.fm>,
intel-gfx@lists.freedesktop.org
Cc: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>,
Jan-Marek Glogowski <glogow@fbihome.de>,
Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Subject: Re: [PATCH 0/2] drm/i915/opregion: proper handling of DIDL and CADL
Date: Fri, 26 Aug 2016 15:12:36 +0300 [thread overview]
Message-ID: <87mvjzsp8r.fsf@intel.com> (raw)
In-Reply-To: <1472151415.3037046.706208097.7301895A@webmail.messagingengine.com>
On Thu, 25 Aug 2016, Paolo Stivanin <paolostivanin@fastmail.fm> wrote:
> Hello,
> I applied these patches[1][2] to the latest kernel revision (
> 4.8.0-rc3-g61c0457) but the brightness keys are not working on my
> laptop.
> With the older patches from the 29th of June the brightness keys were
> working correctly.
Maarten, any ideas? The only changes are the change from crtc->active to
active_crtcs, and the initialization change.
BR,
Jani.
>
> Cheers,
>
> [1] https://patchwork.freedesktop.org/patch/107280/
> [2] https://patchwork.freedesktop.org/patch/107281/
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-26 12:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 12:53 [PATCH 0/2] drm/i915/opregion: proper handling of DIDL and CADL Jani Nikula
2016-08-25 12:53 ` [PATCH 1/2] drm/i915: make i915 the source of acpi device ids for _DOD Jani Nikula
2016-08-25 12:53 ` [PATCH 2/2] drm/i915/opregion: update cadl based on actually active outputs Jani Nikula
2016-08-25 12:59 ` Maarten Lankhorst
2016-08-25 13:20 ` ✗ Fi.CI.BAT: warning for drm/i915/opregion: proper handling of DIDL and CADL Patchwork
2016-08-25 18:56 ` [PATCH 0/2] " Paolo Stivanin
2016-08-26 12:12 ` Jani Nikula [this message]
2016-08-29 6:42 ` Maarten Lankhorst
2016-08-30 19:28 ` Paolo Stivanin
2016-08-31 17:57 ` tasev.stefanoska
2016-08-27 20:51 ` Peter Wu
2016-08-30 1:06 ` Marcos Paulo de Souza
2016-10-31 12:12 ` Rainer Koenig
2016-10-31 12:31 ` Jani Nikula
2016-10-31 12:32 ` Jani Nikula
2016-10-31 23:47 ` Marcos Souza
2016-11-07 12:30 ` Rainer Koenig
2016-11-16 14:32 ` Jani Nikula
2016-11-16 20:14 ` Paolo Stivanin
2016-11-17 1:39 ` Marcos Paulo de Souza
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=87mvjzsp8r.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=glogow@fbihome.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marcos.souza.org@gmail.com \
--cc=paolostivanin@fastmail.fm \
/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.