From: Nick Kossifidis <mick@madwifi.org>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, mcgrof@gmail.com, jirislaby@gmail.com
Subject: [PATCH 0/2] ath5k: Further cleanups inside base.c
Date: Sun, 21 Oct 2007 01:20:30 +0000 [thread overview]
Message-ID: <20071021012030.GA5817@localhost.domain.invalid> (raw)
A few more cleanups for base.c before i submit the rest of my fixes...
Q: Should we get rid of syctl stuff ? I mean user can only change
calibration interval (which is something tricky for users to play with)
and debug flags. Does anyone use this ? i mean we can put printks wherever
we want, there's no need for this stuff IMHO (it comes from madwifi).
next reply other threads:[~2007-10-21 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 1:20 Nick Kossifidis [this message]
2007-10-21 6:43 ` [PATCH 0/2] ath5k: Further cleanups inside base.c Jiri Slaby
2007-10-22 15:00 ` Luis R. Rodriguez
2007-10-22 15:34 ` [ath5k-devel] " Nick Kossifidis
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=20071021012030.GA5817@localhost.domain.invalid \
--to=mick@madwifi.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
/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.