From: Daniel Vetter <daniel@ffwll.ch>
To: "Yang, Guang A" <guang.a.yang@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Updated drm-intel-testing tree
Date: Fri, 12 Jul 2013 21:48:24 +0200 [thread overview]
Message-ID: <20130712194823.GJ6143@phenom.ffwll.local> (raw)
Hi all,
So new testing cycle! Due to rebasing stuff around it's there's almost
some patches from the previous cycle in the git log. But recollecting from
memory we have here:
- First slice of real ppgtt prep stuff from Ben.
- error state in sysfs and independent of CONFIG_DEBUG_FS (Mika)
- interrupt handling code improvements
- and an assorted pile of smaller stuff
In other words: Not much, people are on vacation ;-)
Happy testing!
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next reply other threads:[~2013-07-12 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 19:48 Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-26 19:52 Updated drm-intel-testing tree Daniel Vetter
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=20130712194823.GJ6143@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=guang.a.yang@intel.com \
--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