From: Holger Schurig <h.schurig@mn-solutions.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: RECAP: indication of channel noise
Date: Mon, 26 Oct 2009 15:30:03 +0100 [thread overview]
Message-ID: <200910261530.03422.h.schurig@mn-solutions.de> (raw)
In-Reply-To: <1256565132.12462.9.camel@johannes.local>
> > NL80211_BSS_NOISE_MBM
Hmm, this could better be NL80211_CHANNEL_NOISE_MBM, to make
clear that this is not heat-related internal noise of the chip.
For the rest of your remarks: ok
--
M&N Solutions GmbH Ein Unternehmen der Datagroup AG
Holger Schurig
Raiffeisenstr. 10
61191 Rosbach
Tel: 06003/9141-15 Fax 06003/9141-49
http://www.mn-solutions.de/
Handelsregister Friedberg, HRB 5903
Geschäftsführer: P.Schrittenlocher
next prev parent reply other threads:[~2009-10-26 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 13:42 RECAP: indication of channel noise Holger Schurig
2009-10-26 13:52 ` Johannes Berg
2009-10-26 14:30 ` Holger Schurig [this message]
2009-10-27 3:45 ` Jouni Malinen
2009-10-27 7:03 ` Johannes Berg
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=200910261530.03422.h.schurig@mn-solutions.de \
--to=h.schurig@mn-solutions.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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