From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
Date: Thu, 19 May 2011 18:16:04 GMT [thread overview]
Message-ID: <201105191816.p4JIG4f2007283@demeter2.kernel.org> (raw)
In-Reply-To: <bug-35192-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=35192
--- Comment #6 from Stratos Psomadakis <psomas@ece.ntua.gr> 2011-05-19 18:15:57 ---
The only problem now seems to be with commit 737a3b, which should be reverted,
as it breaks radeon with a non-modular kernel (because of __init_or_module).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2011-05-19 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 0:02 [Bug 35192] New: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300] bugzilla-daemon
2011-05-16 23:38 ` [Bug 35192] " bugzilla-daemon
2011-05-18 21:53 ` bugzilla-daemon
2011-05-18 22:56 ` bugzilla-daemon
2011-05-18 22:58 ` bugzilla-daemon
2011-05-19 14:05 ` bugzilla-daemon
2011-05-19 18:16 ` bugzilla-daemon [this message]
2011-07-05 10:31 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon
2012-06-13 15:06 ` bugzilla-daemon
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=201105191816.p4JIG4f2007283@demeter2.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 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).