From: Bjorge Dijkstra <bjd@jooz.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: status wireless extensions API for new drivers
Date: Fri, 14 Dec 2007 00:01:20 +0100 [thread overview]
Message-ID: <4761B9C0.3080309@jooz.net> (raw)
In-Reply-To: <20071213221323.GF3083@tuxdriver.com>
John W. Linville wrote:
> BTW, how is your patchset looking? If you want it to be in 2.6.25
> then you need to post it soon.
>
It's currently in the form of a seperate self supporting package based
on an older kernel. So that probably needs a little bit of work to get
it rebased on current kernel. It's not a must for me to get it in 2.6.25
though, so if we miss it that's not a problem.
BTW, when is the approx. deadline for 2.6.25?
> FWIW, as long as you have just enough WEXT support to get it to work
> with open networks I think that would be enough to get a patch merged.
> Having experimented a bit earlier with your patchset, I suspect you
> can probably support WEP and maybe more by now...
Yes, WEP, WPA and WPA2 all should work fine. I'm using it everyday on a
WPA2 network with no issues. I don't have a wired connection here, so I
depend on it working for me :)
>
> So, when will we see your patches?
>
I'll try get something out during the weekend.
> Thanks,
>
> John
regards,
Bjorge
next prev parent reply other threads:[~2007-12-13 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 21:15 status wireless extensions API for new drivers Bjorge Dijkstra
2007-12-13 21:31 ` John W. Linville
2007-12-13 22:07 ` Bjorge Dijkstra
2007-12-13 22:13 ` John W. Linville
2007-12-13 23:01 ` Bjorge Dijkstra [this message]
2007-12-13 21:33 ` Dan Williams
2007-12-13 22:05 ` Bjorge Dijkstra
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=4761B9C0.3080309@jooz.net \
--to=bjd@jooz.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.