mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4.19-pre3] New wireless driver API part 1
Date: Wed, 13 Mar 2002 19:11:59 -0800	[thread overview]
Message-ID: <20020313191159.B14095@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020313185915.A14095@bougret.hpl.hp.com> <E16lLnM-0008E8-00@the-village.bc.nu>
In-Reply-To: <E16lLnM-0008E8-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Mar 14, 2002 at 03:20:47AM +0000

On Thu, Mar 14, 2002 at 03:20:47AM +0000, Alan Cox wrote:
> > the new Wireless Extension API to 2.4.X so that they can hack their
> > drivers without having to deal with 2.5.X. This patch just do that, so
> > could you please add that to your tree ?
> 
> Would it be better to leave the patch where said driver people can get it,
> and when they submit drivers needing it (if ever) then merge it ?

	Maybe, maybe not.
	1) Most Wireless LAN driver live outside the kernel. So, their
evolution is somewhat decoupled to the kernel, so the earlier the
patch goes it the better it is for those.
	2) David Gibson, maintainer of the Orinoco driver, told me
that he would merge my new-API orinoco patches in his driver only when
the new API would be in 2.4.x (as you may have noticed, he hasn't
updated 2.5.X for a while). Chicken and Eggs.
	3) Risk is minimal, bloat is minimal. What's the penality of
merging it now ?

	I'm open to suggestions and will do what's best for
everybody. What other people think ?
	But I feel now is a good time (as it seem that 2.4.19 will
have to go through some stabilisation process).

	Thanks for the comment ;-)

	Jean

  reply	other threads:[~2002-03-14  3:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  2:59 Jean Tourrilhes
2002-03-14  3:09 ` Jeff Garzik
2002-03-14  3:19   ` Jean Tourrilhes
2002-03-14 10:43   ` Bjorn Wesen
2002-03-14 10:49     ` Jeff Garzik
2002-03-15  2:35       ` David Gibson
2002-03-16  0:37         ` Oliver Xymoron
2002-03-14 11:52     ` Wichert Akkerman
2002-03-14  3:20 ` Alan Cox
2002-03-14  3:11   ` Jean Tourrilhes [this message]
2002-03-14  3:15     ` Jeff Garzik
2002-03-14  3:25       ` Jean Tourrilhes
2002-03-15  2:43       ` David Gibson
2002-03-15  3:41         ` Jean Tourrilhes
2002-03-14  3:29     ` Alan Cox
2002-03-29  1:08 ` [PATCH 2.4.19-pre4] " 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=20020313191159.B14095@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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®