From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: New stuff in wireless-dev, wireless developers please pull...
Date: Fri, 03 Nov 2006 10:07:52 +0100 [thread overview]
Message-ID: <1162544872.2923.18.camel@ux156> (raw)
In-Reply-To: <20061103043024.GF2989@tuxdriver.com>
On Thu, 2006-11-02 at 23:30 -0500, John W. Linville wrote:
> I've also added a 'pending' branch, with similar policies to the
> 'pending' branch in wireless-2.6 (i.e it means I've got the patch,
> but I'm waiting on some feedback or changes, etc).
Note that the d80211: change the cookie to be opaque as committed is
actually slightly buggy as I pointed out in a follow-up mail, the quilt
dir that's up on my homepage (which is now accessible too...) contains
the fixed version.
> One big addition is the cfg80211/nl80211 stuff from Johannes. I'm not
> quite confident that the Kconfig stuff is right, but the code is there.
Nice :)
johannes
prev parent reply other threads:[~2006-11-03 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 4:30 New stuff in wireless-dev, wireless developers please pull John W. Linville
2006-11-03 6:42 ` Michael Wu
2006-11-03 8:44 ` Johannes Berg
2006-11-03 9:06 ` Johannes Berg
2006-11-03 11:16 ` Johannes Berg
2006-11-03 9:07 ` Johannes Berg [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=1162544872.2923.18.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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).