From: Oleksij Rempel <linux@rempel-privat.de>
To: Guy Harris <guy@alum.mit.edu>
Cc: ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
radiotap@NetBSD.org
Subject: Re: [PATCH] tcpdump: add STBC Rx support
Date: Fri, 03 May 2013 22:04:38 +0200 [thread overview]
Message-ID: <51841856.2090503@rempel-privat.de> (raw)
In-Reply-To: <15EBD372-C4E3-4DA3-9ED9-47B238654587@alum.mit.edu>
Am 03.05.2013 21:58, schrieb Guy Harris:
> You might want to fork the tcpdump Git repository on GitHub:
>
> https://github.com/the-tcpdump-group/tcpdump
>
> make your changes, and submit a pull request for the tcpdump repository; that's the preferred way to submit changes to tcpdump (and, *mutatis mutandis*, to libpcap).
>
Ok, i'll do that. I thought is should be posted first on radiotap list
as part of standardisation process. May be some constructive comments
and change will come ;)
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-05-03 20:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:34 Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-02 20:44 ` Johannes Berg
2013-05-03 19:53 ` Patches for STBC Standartisation Oleksij Rempel
2013-05-03 19:53 ` [PATCH 1/3] mac80211: add STBC flag for radiotap Oleksij Rempel
2013-05-03 19:53 ` [PATCH 2/3] ath9k: remove useless flag conversation Oleksij Rempel
2013-05-03 19:53 ` [PATCH 3/3] ath9k: check for Rx-STBC flag and pass it to ieee80211 Oleksij Rempel
2013-05-03 19:53 ` [PATCH] tcpdump: add STBC Rx support Oleksij Rempel
2013-05-03 19:58 ` Guy Harris
2013-05-03 20:04 ` Oleksij Rempel [this message]
2013-05-04 6:22 ` Patch for radiotap library Oleksij Rempel
2013-05-07 7:40 ` Standardisation - adding 2 bit STBC and Ness to MCS Oleksij Rempel
2013-05-07 13:54 ` Johannes Berg
2013-05-07 13:55 ` Johannes Berg
2013-05-07 14:25 ` Oleksij Rempel
2013-05-07 14:59 ` Jonathan Bither
2013-05-07 15:03 ` Oleksij Rempel
2013-05-07 16:09 ` Jonathan Bither
2013-05-03 21:12 ` Simon Barber
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=51841856.2090503@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=guy@alum.mit.edu \
--cc=linux-wireless@vger.kernel.org \
--cc=radiotap@NetBSD.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).