linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Green <andy@warmcat.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection
Date: Sat, 17 Mar 2007 22:05:02 +0000	[thread overview]
Message-ID: <45FC660E.1090402@warmcat.com> (raw)
In-Reply-To: <200703171730.33349.flamingice@sourmilk.net>

Michael Wu wrote:
> On Saturday 17 March 2007 06:58, andy@warmcat.com wrote:
>> diff --git a/net/mac80211/ieee80211.c b/net/mac80211/ieee80211.c
>> index fb33b90..3873262 100644
>> --- a/net/mac80211/ieee80211.c
>> +++ b/net/mac80211/ieee80211.c
>> @@ -35,6 +35,7 @@
>>  #include "ieee80211_led.h"
>>  #include "ieee80211_cfg.h"
>>  #include "ieee80211_sysfs.h"
>> +#include <net/ieee80211_radiotap.h>
>>
> Already included by my patch.

OK.  Not sure why that appears in my patch any longer then since I am 
using guilt thanks to your advice, and your patch is applied first.

>> +	int tap_index = 0;
>> +	u8 *tap_arg = skb->data + sizeof(struct ieee80211_radiotap_header);
>> +	u32 *curr_arg_bitmap = &rthdr->it_present;
>> +	u32 arg_bitmap=le32_to_cpu(*curr_arg_bitmap);
> Space before and after the =. 

Fixed.

>> +
>> +	if(rthdr->it_version) return TXRX_DROP; /* version byte used as magic */
> Space after the if.

Fixed.

>> +
>> +		/* sanity check for skb length and radiotap length field */
> Keep comments indented the same as everything else.

Fixed.

>> +	if (skb->len < (le16_to_cpu(rthdr->it_len) +
>> +		sizeof(struct ieee80211_hdr)))
> Using some spaces to align the start of the second line with the parenthesis 
> often looks better.

Fixed and noted.

>> +		/* process and remove the injection radiotap header */
>> +
>> +	if(control->flags & IEEE80211_TXCTL_INJECTED_PACKET) {
> dev points to the virtual interface that the frame originally came in on. You 
> can get sdata from that and figure out if the interface was a monitor 
> interface.

replied in next mail...

-Andy

  parent reply	other threads:[~2007-03-17 22:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17 10:58 [PATCH 0/2] Radiotap on Monitor Mode interfaces for rx and tx andy
2007-03-17 10:58 ` [PATCH 1/2] mac80211: Add radiotap support andy
2007-03-17 10:58 ` [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection andy
2007-03-17 13:59   ` Michael Buesch
2007-03-17 14:58     ` Andy Green
2007-03-17 15:06       ` Michael Buesch
2007-03-17 15:35         ` Andy Green
2007-03-17 21:30   ` Michael Wu
2007-03-17 21:51     ` Michael Wu
2007-03-17 22:09       ` Andy Green
2007-03-17 23:20         ` Michael Wu
2007-03-17 23:26           ` Andy Green
2007-03-18  9:00             ` Andy Green
2007-03-18 10:12               ` Andy Green
2007-03-17 22:05     ` Andy Green [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-18 10:15 [PATCH 0/2] Try #3 Radiotap on Monitor Mode interfaces for rx and tx andy
2007-03-18 10:15 ` [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection andy
2007-03-19  5:55   ` Michael Wu
2007-03-19 10:54     ` Andy Green
2007-03-19 16:50       ` Michael Wu
2007-03-21  4:12         ` Joerg Mayer

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=45FC660E.1090402@warmcat.com \
    --to=andy@warmcat.com \
    --cc=flamingice@sourmilk.net \
    --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).