Re: [PATCH] starfire reads irq before pci_enable_device.

[Jeff Garzik <jgarzik@mandrakesoft.com>]

Ion Badulescu wrote:
> On Thu, 8 Feb 2001, Jeff Garzik wrote:
> > The #ifdef ZEROCOPY code you added is a classic example of the kind of
> > code I -remove- from the kernel tree.
> 
> It's an issue of maintainer convenience vs. esthetics. And (last but not
> least) it's also about other people's ability to easily make changes to
> the driver, changes they can understand and test. So while in principle I
> agree with you, I'm also beginning to understand Donald Becker's
> frustration when others remove backward compatibility from his code.
> 
> So let's try to find some middle ground, ok? Your first suggestion sounds
> reasonable, and hopefully the fate of the zerocopy stuff will be decided
> sooner than later.

I would prefer that zerocopy code remain out of all official kernels
until zerocopy itself is in said kernels.  It's experimental code that
simply cannot work in its present form, due to lack of infrastructure in
the general kernel.  And being based on experimental code itself, there
is definitely the potential for changes yet.

Remember:  we are in a stable series of kernels.  This is experimental
code.  Maintain a separate branch of development like everyone else. 
:)   Yes it's a bit more effort, but that's what being a maintainer is
all about.  The kernel needs a -stable- starfire.c, let's talk about
adding experimental code later.

BTW, I would suggest looking at Jes' acenic.c as an example of a 2.4
driver that is clean but also [hopefully!] works under 2.2.

	Jeff


-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/