From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] Wireless Extension v17 (resend)
Date: Tue, 8 Feb 2005 16:41:46 -0200 [thread overview]
Message-ID: <20050208184145.GD10799@logos.cnet> (raw)
In-Reply-To: <20050208215112.GB3290@bougret.hpl.hp.com>
On Tue, Feb 08, 2005 at 01:51:12PM -0800, Jean Tourrilhes wrote:
> On Tue, Feb 08, 2005 at 04:01:16PM -0200, Marcelo Tosatti wrote:
> >
> > Hi Jean,
> >
> > I'm very ignorant about wireless but it doesnt appear to me that "Wireless Extension v17"
> > is a critical feature.
>
> You are right, it's not critical, and I was already thinking
> of not pushing WE-18 to you (the WPA update). I'll stop updating 2.4.X
> with respect to wireless, the patches will be available on my web page
> for people who needs it.
Please dont miss bugfixes for present functionality. Gracias.
> We may revisit this if there is a public
> outcry...
OK!
> > It seems more appropriate to declare it as 2.6 functionality ?
>
> There need to be some unique features in 2.6.X to force people
> to upgrade, I guess...
Faster, cleaner, way more elegant, handles intense loads more gracefully,
handles highmem decently, LSM/SELinux, etc, etc...
IMO everyone should upgrade whenever appropriate.
next prev parent reply other threads:[~2005-02-08 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 18:16 [PATCH 2.4] Wireless Extension v17 (resend) Jean Tourrilhes
2005-02-08 18:01 ` Marcelo Tosatti
2005-02-08 21:51 ` Jean Tourrilhes
2005-02-08 18:41 ` Marcelo Tosatti [this message]
2005-02-08 22:45 ` Willy Tarreau
2005-02-08 20:05 ` Marcelo Tosatti
2005-02-09 0:37 ` Jean Tourrilhes
2005-02-09 1:51 ` Chris Wright
2005-02-09 2:07 ` Jean Tourrilhes
2005-02-09 2:17 ` Chris Wright
2005-02-09 1:09 ` kernel
2005-02-08 22:28 ` Marcelo Tosatti
2005-02-09 1:21 ` kernel
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=20050208184145.GD10799@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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 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.