From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trouble with DWA-552 and ath9k
Date: Fri, 15 Jan 2010 00:40:23 -0500 [thread overview]
Message-ID: <1263534023.2655.8.camel@ct> (raw)
In-Reply-To: <1263510788.18918.10.camel@mj>
On Thu, 2010-01-14 at 18:13 -0500, Pavel Roskin wrote:
> If you want to create a bug report, please use bugzilla.kernel.org.
Maybe we could open a bug and then write something like this on the
ath9k page:
D-Link DWL-552 (revision X is affected by the bug NNN)
Ubiquiti SR71-12 (affected by the bug NNN)
This way, the users will be able to see if the bug has been fixed and in
which kernel revisions. At the same time, the ath9k page won't be
littered with unmaintainable information.
The same rule could be used elsewhere in the Linux wireless wiki. That
is, any references to bugs are only acceptable is accompanied with a
link to the bug tracker.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-01-15 5:40 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:43 [ath9k-devel] trouble with DWA-552 and ath9k Brian Walker
2009-12-18 3:12 ` Sujith
2009-12-18 3:51 ` Brian Walker
2009-12-18 4:44 ` Sujith
2009-12-18 11:55 ` Brian Walker
2009-12-19 3:05 ` Brian Walker
2009-12-22 4:58 ` Sujith
[not found] ` <4B30D348.3080600@charter.net>
2009-12-22 18:39 ` Brian Walker
2009-12-28 19:22 ` Brian Walker
2009-12-28 20:49 ` Pavel Roskin
2009-12-28 21:06 ` Brian Walker
2009-12-28 21:28 ` Pavel Roskin
2009-12-28 22:54 ` Brian Walker
2009-12-29 15:02 ` Pavel Roskin
2009-12-29 23:23 ` Brian Walker
2009-12-30 6:16 ` Pavel Roskin
2010-01-05 16:49 ` Brian Walker
2010-01-08 4:34 ` Sujith
2010-01-09 15:14 ` Brian Walker
2010-01-09 15:38 ` Pavel Roskin
2010-01-09 19:33 ` Brian Walker
2010-01-10 5:12 ` Sujith
2010-01-11 18:42 ` Brian Walker
2010-01-13 1:18 ` Brian Walker
2010-01-13 8:04 ` Sujith
2010-01-13 15:35 ` Pavel Roskin
2010-01-13 17:28 ` Pavel Roskin
2010-01-14 2:58 ` Brian Walker
2010-01-14 6:15 ` Pavel Roskin
2010-01-14 11:51 ` Brian Walker
2010-01-14 23:13 ` Pavel Roskin
2010-01-15 5:40 ` Pavel Roskin [this message]
2010-01-16 16:27 ` Brian Walker
2010-01-20 23:03 ` Pavel Roskin
2010-01-25 18:47 ` Brian Walker
2010-01-25 19:34 ` Pavel Roskin
2010-01-27 0:52 ` Brian Walker
2010-01-27 23:13 ` Pavel Roskin
2010-01-28 0:36 ` Brian Walker
2010-02-05 19:13 ` Brian Walker
2010-02-05 19:34 ` Pavel Roskin
2010-02-06 0:56 ` Brian Walker
2010-02-06 5:20 ` Pavel Roskin
2010-02-10 1:00 ` Brian Walker
2010-02-10 19:24 ` Pavel Roskin
2010-02-10 19:57 ` Brian Walker
2010-02-20 3:00 ` Brian Walker
2010-02-23 21:30 ` Pavel Roskin
2010-02-24 1:21 ` Brian Walker
2010-02-24 6:09 ` [ath9k-devel] hostapd-0.7-1 failed work with ath9k Zhang Yanfei-B21500
2010-02-24 6:42 ` Pavel Roskin
2010-03-02 10:20 ` yingqiang Ma
2010-03-03 2:01 ` Zhang Yanfei-B21500
2010-02-24 6:40 ` [ath9k-devel] trouble with DWA-552 and ath9k Pavel Roskin
2010-02-24 13:21 ` Brian Walker
2010-02-24 18:09 ` Pavel Roskin
2010-02-24 18:14 ` Pavel Roskin
2010-02-25 18:31 ` Pavel Roskin
2010-02-25 20:34 ` Peter Stuge
2010-02-26 1:10 ` Brian Walker
2010-02-26 23:35 ` Pavel Roskin
2010-03-02 0:48 ` Brian Walker
2010-03-03 4:31 ` Pavel Roskin
2010-03-02 0:55 ` Brian Walker
2010-03-03 4:33 ` Pavel Roskin
2010-03-08 2:20 ` Brian Walker
-- strict thread matches above, loose matches on Subject: below --
2009-12-17 19:52 Brian Walker
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=1263534023.2655.8.camel@ct \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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 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.