From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: wireless@lists.tuxdriver.org
Subject: Re: [RFC] cfg80211 merge
Date: Wed, 31 Jan 2007 22:06:01 +0100 [thread overview]
Message-ID: <1170277561.2236.6.camel@johannes.berg> (raw)
In-Reply-To: <20070131204438.GB19669@tuxdriver.com>
[-- Attachment #1.1: Type: text/plain, Size: 270 bytes --]
On Wed, 2007-01-31 at 15:44 -0500, John W. Linville wrote:
> Agreed. I (and/or Johannes?) will rework the patches to remove the
> nl bits.
Starting tomorrow I can devote some time again.
Maybe we should resurrect those wiphy patches I had first?
johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
wireless mailing list
wireless@lists.tuxdriver.org
http://lists.tuxdriver.org/mailman/listinfo/wireless
next prev parent reply other threads:[~2007-01-31 21:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 1:37 [RFC] cfg80211 merge John W. Linville
2007-01-31 1:38 ` [RFC PATCH 1/3] cfg80211 and nl80211 John W. Linville
2007-01-31 1:39 ` [RFC PATCH 2/3] wireless: move wext to net/wireless/ John W. Linville
2007-01-31 1:41 ` [RFC PATCH 3/3] cfg80211: add wext-compatible client John W. Linville
2007-01-31 14:40 ` [RFC PATCH 2/3] wireless: move wext to net/wireless/ Christoph Hellwig
2007-01-31 19:00 ` Johannes Berg
2007-01-31 2:46 ` [RFC PATCH 1/3] cfg80211 and nl80211 Michael Wu
2007-01-31 17:37 ` Jiri Benc
2007-01-31 20:24 ` Michael Buesch
2007-02-01 10:18 ` Johannes Berg
2007-02-05 17:45 ` Michael Wu
2007-02-05 17:49 ` Johannes Berg
2007-02-05 18:14 ` Michael Wu
2007-02-05 18:14 ` Johannes Berg
2007-02-05 18:29 ` Jiri Benc
2007-02-05 18:29 ` Johannes Berg
2007-02-05 19:13 ` Jouni Malinen
2007-02-05 19:23 ` Michael Wu
2007-02-05 19:24 ` Johannes Berg
2007-02-05 19:55 ` Michael Wu
2007-02-09 16:14 ` Johannes Berg
2007-02-05 18:16 ` Jiri Benc
2007-01-31 2:48 ` [RFC] cfg80211 merge Jouni Malinen
2007-01-31 17:29 ` Jiri Benc
2007-01-31 18:32 ` John W. Linville
2007-01-31 19:25 ` Jiri Benc
2007-01-31 20:07 ` Christoph Hellwig
2007-01-31 20:44 ` John W. Linville
2007-01-31 21:06 ` Johannes Berg [this message]
2007-01-31 23:54 ` Tomas Winkler
2007-02-01 13:07 ` Johannes Berg
2007-02-01 14:04 ` Tomas Winkler
2007-02-01 14:11 ` Johannes Berg
2007-02-02 18:18 ` Tomas Winkler
2007-02-03 17:37 ` Johannes Berg
2007-02-01 14:12 ` Jiri Benc
2007-02-07 0:46 ` [RFC v2] " John W. Linville
2007-02-07 0:47 ` [RFC PATCH 1/3] wireless: add cfg80211 John W. Linville
[not found] ` <20070207004832.GC23096@tuxdriver.com>
2007-02-07 0:49 ` [RFC PATCH 3/3] cfg80211: add wext-compatible client John W. Linville
2007-02-07 7:54 ` Christoph Hellwig
2007-02-08 13:13 ` Johannes Berg
2007-02-08 18:38 ` Luis R. Rodriguez
2007-02-08 18:50 ` John W. Linville
2007-02-08 19:41 ` Luis R. Rodriguez
2007-02-09 15:43 ` Johannes Berg
2007-02-08 19:55 ` Christoph Hellwig
2007-02-08 21:56 ` Luis R. Rodriguez
2007-02-09 2:09 ` Dan Williams
2007-02-07 7:35 ` [RFC PATCH 1/3] wireless: add cfg80211 Christoph Hellwig
2007-02-08 13:12 ` Johannes Berg
2007-02-08 19:17 ` Christoph Hellwig
2007-02-07 14:39 ` [RFC v2] cfg80211 merge John W. Linville
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=1170277561.2236.6.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=wireless@lists.tuxdriver.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.