mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	prism54-devel@prism54.org, netdev@oss.sgi.com,
	jgarzik@redhat.com
Subject: Re: [Prism54-devel] Re: Prism54 in 2.6.4-bk2
Date: Tue, 16 Mar 2004 01:47:58 -0500	[thread overview]
Message-ID: <20040316064758.GI24063@ruslug.rutgers.edu> (raw)
In-Reply-To: <40569B4B.2020402@pobox.com>

On Tue, Mar 16, 2004 at 01:14:35AM -0500, Jeff Garzik wrote:
> Luis R. Rodriguez wrote:
> >Regarding WDS on prism54: on the netdev list we discussed this
> >but no one got back to me as to whether we should really just nuke this
> >code. Prism54 driver source *does* include WDS support because hey, the
> >firmware does. Why wouldn't it go in the driver? We haven't given WDS
> >much though anyway since it's also been low priority on our TODO list.
> 
> The WDS code was dead code as merged.
> 
> If you actually use it, I don't mind adding it :)

I don't know of anybody who uses it. We did consider to drop it but we
just never got around to deciding what we were going to do about it. I
know it's there and it's *supposed* to work. 

Can we get back to you on that?  :)  It is just code that *is*
driver/hardware specific.

Actually can I just send you a patch for 2.6 for the latest 2.6 tree to
match ours? That is, rm -rf prism54/ as is and add our latest patch ?
It'd save a lot of work on our end.

We'll still do the 2.6 / 2.4 split and clean the 2.6 code of 2.4 code,
but can you just give us the opportunity to do it from within our tree?

It'd cure many headaches (on our end at least).

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

  reply	other threads:[~2004-03-16  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.2.20040313180709.00ab4250@pop.t-online.de>
     [not found] ` <1079199572.7111.0.camel@lapy.tuxslare.org>
     [not found]   ` <20040313203058.GY32439@ruslug.rutgers.edu>
2004-03-13 22:15     ` Luis R. Rodriguez
2004-03-16  6:14       ` Jeff Garzik
2004-03-16  6:47         ` Luis R. Rodriguez [this message]
2004-03-16  7:01           ` [Prism54-devel] " Jeff Garzik

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=20040316064758.GI24063@ruslug.rutgers.edu \
    --to=mcgrof@ruslug.rutgers.edu \
    --cc=jgarzik@pobox.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@studorgs.rutgers.edu \
    --cc=netdev@oss.sgi.com \
    --cc=prism54-devel@prism54.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

all inboxes | Powered by JetHome®