From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic/drm-fixes
Date: Thu, 02 Apr 2015 11:17:15 +0300 [thread overview]
Message-ID: <87mw2rrlkk.fsf@intel.com> (raw)
Hi Dave -
Here's a single drm core fix, cc: stable, that affects i915
users. Picked it up myself as explained in [1].
I'll still send a separate drm/i915 pull request.
BR,
Jani.
[1] http://mid.gmane.org/874mp6r6bk.fsf@intel.com
The following changes since commit bc465aa9d045feb0e13b4a8f32cc33c1943f62d6:
Linux 4.0-rc5 (2015-03-22 16:50:21 -0700)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/topic/drm-fixes-2015-04-02
for you to fetch changes up to ad692b46dbf122ef90aadce3b389ef64c90e861d:
drm/edid: set ELD for firmware and debugfs override EDIDs (2015-03-27 13:27:04 +0200)
----------------------------------------------------------------
Jani Nikula (1):
drm/edid: set ELD for firmware and debugfs override EDIDs
drivers/gpu/drm/drm_edid_load.c | 1 +
drivers/gpu/drm/drm_probe_helper.c | 1 +
2 files changed, 2 insertions(+)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-04-02 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 8:17 Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 11:37 [PULL] topic/drm-fixes Jani Nikula
2015-07-03 23:07 Daniel Vetter
2015-07-15 8:52 Daniel Vetter
2015-07-15 9:16 ` Daniel Vetter
2015-07-16 6:44 Daniel Vetter
2015-07-23 6:53 Daniel Vetter
2015-08-14 10:03 Jani Nikula
2015-11-11 11:41 Jani Nikula
2015-11-19 16:00 Jani Nikula
2016-04-07 9:05 Jani Nikula
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=87mw2rrlkk.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).