From: "John W. Linville" <linville@tuxdriver.com>
To: rt2400-devel@lists.sourceforge.net
Cc: linux-wireless@vger.kernel.org
Subject: bug in rt2x00debug_deregister?
Date: Thu, 22 Mar 2007 13:47:31 -0400 [thread overview]
Message-ID: <20070322174731.GG3860@tuxdriver.com> (raw)
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233345
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233434
Seeing some oopsen w/ the rt2x00 driver currently in Fedora rawhide.
That version does not have the most recent round of patches I merged
to wireless-dev a couple of days ago, FWIW.
I think it would be great if Ivo or some other rt2x00 developers
would register in Red Hat's bugzilla so that I can CC: them on bugs --
please let me know if anyone is amenable to that.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next reply other threads:[~2007-03-22 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 17:47 John W. Linville [this message]
2007-03-22 18:23 ` bug in rt2x00debug_deregister? Ivo van Doorn
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=20070322174731.GG3860@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-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).