From: "Antti Koskipää" <antti.koskipaa@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Bug team status
Date: Fri, 21 Dec 2012 15:05:11 +0200 [thread overview]
Message-ID: <50D45E87.2000608@linux.intel.com> (raw)
Another bug team week gone...
Antti:
Went through bugzilla, checking that work is still being done, general
stuff.
Mika:
Fixed https://bugs.freedesktop.org/show_bug.cgi?id=58230
Tried to verify a fix (drm/i915: disable shrinker lock
stealing for create_mmap_offset) for a problem i reported
but didn't manage to get ./gem_tiled_swapping to break anymore on
top of clean of clean drm-intel-fixes.
Rodrigo:
Worked on https://bugs.freedesktop.org/show_bug.cgi?id=51146
and https://bugs.freedesktop.org/show_bug.cgi?id=54964 and may have
found a VGA workaround for the latter one.
--
- Antti
next reply other threads:[~2012-12-21 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 13:05 Antti Koskipää [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-04 18:05 Bug Team Status Paulo Zanoni
2013-01-28 16:36 Rodrigo Vivi
2013-01-14 14:21 Jani Nikula
2012-12-03 16:21 Damien Lespiau
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=50D45E87.2000608@linux.intel.com \
--to=antti.koskipaa@linux.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