From: Jani Nikula <jani.nikula@intel.com>
To: Paolo Stivanin <paolostivanin@fastmail.fm>,
Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>,
intel-gfx@lists.freedesktop.org
Cc: Jan-Marek Glogowski <glogow@fbihome.de>,
Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/3] drm/i915/opregion: proper handling of DIDL, and some hacks on CADL
Date: Fri, 18 Nov 2016 10:27:07 +0200 [thread overview]
Message-ID: <871sy9yyzo.fsf@intel.com> (raw)
In-Reply-To: <1479408202.1350142.791269785.26733F8B@webmail.messagingengine.com>
On Thu, 17 Nov 2016, Paolo Stivanin <paolostivanin@fastmail.fm> wrote:
> Hello,
> I can confirm that patch 3 is not needed.
> I applied only patch 1 and 2 and everything works super fine!
Thanks for confirming this.
BR,
Jani.
--
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-11-18 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:29 [PATCH 0/3] drm/i915/opregion: proper handling of DIDL, and some hacks on CADL Jani Nikula
2016-11-16 11:29 ` [PATCH 1/3] drm/i915: make i915 the source of acpi device ids for _DOD Jani Nikula
2016-11-16 11:29 ` [PATCH 2/3] drm/i915/opregion: fill in the CADL from connector list, not DIDL Jani Nikula
2016-11-16 11:29 ` [PATCH 3/3] drm/i915/opregion: put internal panels to the front of CADL Jani Nikula
2016-11-16 12:46 ` ✗ Fi.CI.BAT: failure for drm/i915/opregion: proper handling of DIDL, and some hacks on CADL Patchwork
2016-11-17 9:24 ` [PATCH 0/3] " Rainer Koenig
2016-11-17 11:01 ` Jani Nikula
2016-11-17 18:43 ` Paolo Stivanin
2016-11-18 8:27 ` Jani Nikula [this message]
2016-11-21 9:17 ` Peter Wu
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=871sy9yyzo.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Rainer.Koenig@ts.fujitsu.com \
--cc=daniel.vetter@ffwll.ch \
--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.