From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times?
Date: Sun, 7 Feb 2010 09:11:20 GMT [thread overview]
Message-ID: <201002070911.o179BKdN029876@demeter.kernel.org> (raw)
In-Reply-To: <bug-15245-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15245
Rafael J. Wysocki <rjw@sisk.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Video(Other) |Video(DRI - non Intel)
AssignedTo|drivers_video-other@kernel- |drivers_video-dri@kernel-bu
|bugs.osdl.org |gs.osdl.org
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
next parent reply other threads:[~2010-02-07 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15245-2300@http.bugzilla.kernel.org/>
2010-02-07 9:11 ` bugzilla-daemon [this message]
2010-02-07 20:04 ` [Bug 15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times? bugzilla-daemon
2010-02-11 14:01 ` bugzilla-daemon
2010-02-12 18:18 ` bugzilla-daemon
2010-02-12 18:21 ` bugzilla-daemon
2010-02-12 23:52 ` [Bug 15245] [2.6.33-rc6 " bugzilla-daemon
2010-02-07 22:16 2.6.33-rc7: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-07 22:28 ` [Bug #15245] [2.6.33-rc6 fc76be4 w/ drm-radon-testing and KMS enabled] Weird JCPU times? Rafael J. Wysocki
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=201002070911.o179BKdN029876@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.