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: Wed, 11 Nov 2015 13:41:34 +0200 [thread overview]
Message-ID: <87bnb0ix01.fsf@intel.com> (raw)
Hi Dave, I seem to be off-sync with your pulls to Linus... anyway,
here's one uapi build fix I've picked up.
BR,
Jani.
The following changes since commit f36203be608a38a5b5523a7aa52cc72f757b9679:
drm/dp: Add dp_aux_i2c_speed_khz module param to set the assume i2c bus speed (2015-09-02 16:13:43 +0300)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/topic/drm-fixes-2015-11-11
for you to fetch changes up to 6172180c6b37ea164bf8a9bad70bb348d0a16563:
drm: Use userspace compatible type in fourcc_mod_code macro (2015-11-05 14:39:55 +0200)
----------------------------------------------------------------
Tvrtko Ursulin (1):
drm: Use userspace compatible type in fourcc_mod_code macro
include/uapi/drm/drm_fourcc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-11-11 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 11:41 Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-07 9:05 [PULL] topic/drm-fixes Jani Nikula
2015-11-19 16:00 Jani Nikula
2015-08-14 10:03 Jani Nikula
2015-07-23 6:53 Daniel Vetter
2015-07-16 6:44 Daniel Vetter
2015-07-15 8:52 Daniel Vetter
2015-07-15 9:16 ` Daniel Vetter
2015-07-03 23:07 Daniel Vetter
2015-05-27 11:37 Jani Nikula
2015-04-02 8:17 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=87bnb0ix01.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).