From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
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 02:01:16 -0500 [thread overview]
Message-ID: <4056A63C.50808@pobox.com> (raw)
In-Reply-To: <20040316064758.GI24063@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> 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.
For code is that (a) experimental, (b) for pre-production hardware, or
(c) rarely if ever used, we would prefer to not merge it at all.
When I see stuff like "TODO: actually give this some thought" and "I
don't know anybody who uses it", that means it doesn't need to be merged
in the upstream tree :)
> 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.
It depends on how big the patch is, and whether or not it adds code that
nobody but the dev team uses, etc... I don't want to add the WDS code,
since nobody uses it... and adding the #ifdefs I removed would not be
desired either. Those #ifdefs aren't need in the upstream tree. I plan
to remove them from other upstream drivers, too.
WRT submitting patches... send away. drivers/net patches should go ->
Jean T -> jgarzik+netdev or simply -> jgarzik+netdev, your choice. In
general "50 small patches are better than 1 big patch". Large updates
are not reviewable or easily testable. Large patches tend to fix 20
bugs, and add 5 new ones.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
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 02:01:16 -0500 [thread overview]
Message-ID: <4056A63C.50808@pobox.com> (raw)
In-Reply-To: <20040316064758.GI24063@ruslug.rutgers.edu>
Luis R. Rodriguez wrote:
> 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.
For code is that (a) experimental, (b) for pre-production hardware, or
(c) rarely if ever used, we would prefer to not merge it at all.
When I see stuff like "TODO: actually give this some thought" and "I
don't know anybody who uses it", that means it doesn't need to be merged
in the upstream tree :)
> 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.
It depends on how big the patch is, and whether or not it adds code that
nobody but the dev team uses, etc... I don't want to add the WDS code,
since nobody uses it... and adding the #ifdefs I removed would not be
desired either. Those #ifdefs aren't need in the upstream tree. I plan
to remove them from other upstream drivers, too.
WRT submitting patches... send away. drivers/net patches should go ->
Jean T -> jgarzik+netdev or simply -> jgarzik+netdev, your choice. In
general "50 small patches are better than 1 big patch". Large updates
are not reviewable or easily testable. Large patches tend to fix 20
bugs, and add 5 new ones.
Jeff
next prev parent reply other threads:[~2004-03-16 7:08 UTC|newest]
Thread overview: 6+ 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 ` Prism54 in 2.6.4-bk2 Luis R. Rodriguez
2004-03-16 6:14 ` Jeff Garzik
2004-03-16 6:47 ` [Prism54-devel] " Luis R. Rodriguez
2004-03-16 6:47 ` Luis R. Rodriguez
2004-03-16 7:01 ` Jeff Garzik [this message]
2004-03-16 7:01 ` 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=4056A63C.50808@pobox.com \
--to=jgarzik@pobox.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@ruslug.rutgers.edu \
--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 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.