linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: andy@warmcat.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] iwl3945: provide frequency to radiotap monitor not  channel index
Date: Thu, 12 Jul 2007 09:40:48 +0800	[thread overview]
Message-ID: <1184204448.13298.66.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070708201701.126477512@warmcat.com>

On Sun, 2007-07-08 at 21:16 +0100, andy@warmcat.com wrote:
> iwl3945 and presumably 4965 wrongly provide the channel index to the
> radiotap
> header on Monitor mode.  This results in tcpdump showing "6MHz" for
> example.
> 
> This patch arranges to send the frequency in MHz instead eg, 2437MHz
> 
> Signed-off-by: Andy Green <andy@warmcat.com> 

Acked-by: Zhu Yi <yi.zhu@intel.com>

      reply	other threads:[~2007-07-12  1:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 20:16 [PATCH 0/1] iwlwifi: Report MHz not channel index andy
2007-07-08 20:16 ` [PATCH 1/1] iwl3945: provide frequency to radiotap monitor " andy
2007-07-12  1:40   ` Zhu Yi [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=1184204448.13298.66.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=andy@warmcat.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;
as well as URLs for NNTP newsgroup(s).