From: Krzysztof Halasa <khc@pm.waw.pl>
To: bruno randolf <bruno@thinktube.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath5k bf=xxx bf_skb=0 warnings
Date: Tue, 26 Feb 2008 14:32:34 +0100 [thread overview]
Message-ID: <m33arfaln1.fsf@maximus.localdomain> (raw)
In-Reply-To: <200802261511.25472.bruno@thinktube.com> (bruno randolf's message of "Tue\, 26 Feb 2008 15\:11\:25 +0900")
bruno randolf <bruno@thinktube.com> writes:
> yes, that's normal and harmless. i haven't got around to make a smarter
> solution yet.
>
> that's because we call ath5k_beacon_config() each time after a channel is set
> or the chip is reset, even if the beacon has not been configured yet.
I see, thanks.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-02-26 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 3:37 ath5k bf=xxx bf_skb=0 warnings Krzysztof Halasa
2008-02-26 6:11 ` bruno randolf
2008-02-26 13:32 ` Krzysztof Halasa [this message]
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=m33arfaln1.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=bruno@thinktube.com \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox