From: bruno randolf <bruno@thinktube.com>
To: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
Cc: ath5k-devel@lists.ath5k.org, jirislaby@gmail.com,
mickflemm@gmail.com, linux-wireless@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: [PATCH 1/4] ath5k: debug level improvements
Date: Sat, 19 Jan 2008 11:47:04 +0900 [thread overview]
Message-ID: <200801191147.04877.bruno@thinktube.com> (raw)
In-Reply-To: <43e72e890801181526gaf5960fr5c66b97155e8bfda@mail.gmail.com>
On Saturday 19 January 2008 08:26:38 Luis R. Rodriguez wrote:
> On Jan 18, 2008 7:50 AM, Bruno Randolf <bruno@thinktube.com> wrote:
> > + { ATH5K_DEBUG_ANY, "any", "show any debug level" },
>
> Very cool, can we call this "all" instead though, and "show all debug
> levels" ?
>
> Acked-by: Luis R. Rodriguez <mcgrof@winlab.rutgers.edu>
>
> Luis
sure. i'll resend in a minute, also including jiri's hint.
bruno
next prev parent reply other threads:[~2008-01-19 2:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 12:50 [PATCH 1/4] ath5k: debug level improvements Bruno Randolf
2008-01-18 12:50 ` [PATCH 2/4] ath5k: always extend rx timestamp with tsf Bruno Randolf
2008-01-19 22:20 ` Luis R. Rodriguez
2008-01-20 2:12 ` [ath5k-devel] " Derek Smithies
2008-01-18 12:51 ` [PATCH 3/4] ath5k: use 3 instead of 0x00000003 Bruno Randolf
2008-01-19 22:24 ` Luis R. Rodriguez
2008-01-22 1:36 ` Nick Kossifidis
2008-01-18 12:51 ` [PATCH 4/4] ath5k: beacon interval is in TU Bruno Randolf
2008-01-19 22:42 ` Luis R. Rodriguez
2008-01-22 1:29 ` Nick Kossifidis
2008-01-18 12:55 ` [PATCH 1/4] ath5k: debug level improvements Jiri Slaby
2008-01-19 2:43 ` bruno randolf
2008-01-18 23:26 ` Luis R. Rodriguez
2008-01-19 2:47 ` bruno randolf [this message]
2008-01-19 2:49 ` [PATCH] " Bruno Randolf
2008-01-19 10:21 ` Jiri Slaby
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=200801191147.04877.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@winlab.rutgers.edu \
--cc=mickflemm@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.