mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>
Subject: Re: Updated Wireless Extension patches
Date: Tue, 29 Jun 2004 15:45:25 -0400	[thread overview]
Message-ID: <20040629194525.GF23191@havoc.gtf.org> (raw)
In-Reply-To: <20040629162339.GA4356@bougret.hpl.hp.com>

On Tue, Jun 29, 2004 at 09:23:39AM -0700, Jean Tourrilhes wrote:
> 	Hi all,
> 
> 	I've been working a bit more on my current set of Wireless
> Extension patches (WPA, Wireless-RtNetlink, ...). I've just updated
> them on my personal web page :
> 	http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html#wext
> 
> 	The main change is that I'm now happy of the format of
> Wireless over RtNetlink, so it should be close to definitive. I've
> also split all the minor changes as a separate patch (WE-17), so it
> doesn't have to wait for WPA and Wireless-RtNetlink that still need a
> bit of work, and I plan to push this patch soon.
> 	You will also find patches for various drivers to take
> advantage of the new features. I would like to thank the various
> driver authors that sent me patches, suggestions and comments, and
> thank them for their patience.

Regardless of our recent discussions, I do want to emphasize that I wish
to maintain the current WE, and its backwards compatibility, for the
current 2.6.x stable series at the very least.

So please don't be discouraged from submitting WE patches...

	Jeff


P.S. do associated userland wireless-tools patches exist to make use of
netlink?  i.e. how have you been testing it?

  reply	other threads:[~2004-06-29 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 16:23 Jean Tourrilhes
2004-06-29 19:45 ` Jeff Garzik [this message]
2004-06-29 20:41   ` Jean Tourrilhes

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=20040629194525.GF23191@havoc.gtf.org \
    --to=jgarzik@pobox.com \
    --cc=davem@redhat.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®