From: Holger Schurig <holgerschurig@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k/mac80211 and 802.11n in IBSS mode
Date: Mon, 12 Apr 2010 08:40:10 +0200 [thread overview]
Message-ID: <201004120840.10990.holgerschurig@gmail.com> (raw)
In-Reply-To: <4BBF902B.7040504@free.fr>
> Exactly :-). I need to dig into iw source code and understand a bit of
> nl80211 before...
It's not that difficult: use "git log" to look after a patch that added
something interesting to iw as well. The "git show" that patch. Now you'll
find out which places to patch.
Adding nl80211-stuff to the kernel involves much dumb boilerplate!
--
http://www.holgerschurig.de
WARNING: multiple messages have this Message-ID (diff)
From: Holger Schurig <holgerschurig@gmail.com>
To: Benoit PAPILLAULT <benoit.papillault@free.fr>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Joerg Pommnitz <pommnitz@yahoo.com>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] ath9k/mac80211 and 802.11n in IBSS mode
Date: Mon, 12 Apr 2010 08:40:10 +0200 [thread overview]
Message-ID: <201004120840.10990.holgerschurig@gmail.com> (raw)
In-Reply-To: <4BBF902B.7040504@free.fr>
> Exactly :-). I need to dig into iw source code and understand a bit of
> nl80211 before...
It's not that difficult: use "git log" to look after a patch that added
something interesting to iw as well. The "git show" that patch. Now you'll
find out which places to patch.
Adding nl80211-stuff to the kernel involves much dumb boilerplate!
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2010-04-12 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 10:03 [ath9k-devel] ath9k/mac80211 and 802.11n in IBSS mode Joerg Pommnitz
2010-04-09 10:03 ` Joerg Pommnitz
2010-04-09 14:17 ` [ath9k-devel] " Johannes Berg
2010-04-09 14:17 ` Johannes Berg
2010-04-09 20:38 ` [ath9k-devel] " Benoit PAPILLAULT
2010-04-09 20:38 ` Benoit PAPILLAULT
2010-04-12 6:40 ` Holger Schurig [this message]
2010-04-12 6:40 ` Holger Schurig
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=201004120840.10990.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.