From: Christoph Hellwig <hch@infradead.org>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Christoph Hellwig <hch@infradead.org>,
"Kilau, Scott" <Scott_Kilau@digi.com>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>,
Wen Xiong <wendyx@us.ibm.com>
Subject: Re: Digi Neo 8: linux-2.6.12_r2 jsm driver
Date: Wed, 13 Apr 2005 08:26:46 +0100 [thread overview]
Message-ID: <20050413072646.GA32634@infradead.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0504122258510.1894-100000@sweetums.bluetronic.net>
On Tue, Apr 12, 2005 at 11:27:44PM -0400, Ricky Beam wrote:
> As an outside observer, I think he's given you plenty of reason to not
> include this "hack". You, however, appear to only want to make a mess.
Why do you consider it a mess, and what reason did you see?
The jsm driver is an effort where people like Wen Xiong, Al Viro and me
put in a lot of effort to make the piece of crap the digi driver was into
something almost sane. Now we should limit it to a tiny subset of the
supported hardware just because digi is full of crack?
> This is entirely the attitude the denouncers of open source live for. It
> shows the complete lake of respect for the wishes of the maintainer(s).
While Scott wrote most of the original code that ended up in the jsm driver
he's certainly not the maintainer in any sense.
> they "give" you their code. (If it's already GPL'd, there's nothing legally
> stopping the code from being included in the first place, so why must they
> ask for and/or ok inclusion? Answer: good will within the community which
> you are now pissing all over.)
But the original code isn't technically suitable.
> Am I the only one with his eyes open here? When I read the first reply from
> Scott, I was thinking, "why not just make it a config option? What's the
> big f***ing deal?" Make it a config option with help text pointing people
> to the "better" driver with improved features and support for that board.
> Or something as simple as "don't enable this if you're going to use this
> other dirver."
Because a config option is totally pointless. If Scott wants someone to
use his driver he can that person to simply load that driver, there's
absolutely no reason for us to cripple our drivers because some vendor
has out of tree drivers. We don't remove support for card from tg3 just
because Broadcom would prefer us to use their bcm5700 driver, or remove
support for cards from the 3c59x driver just because 3com has a driver of
their own for a few of those cards.
next prev parent reply other threads:[~2005-04-13 7:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 15:30 Digi Neo 8: linux-2.6.12_r2 jsm driver Kilau, Scott
2005-04-12 15:32 ` Christoph Hellwig
2005-04-13 3:27 ` Ricky Beam
2005-04-13 7:26 ` Christoph Hellwig [this message]
2005-04-12 16:16 ` Greg KH
2005-04-12 16:23 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2005-04-13 14:25 Kilau, Scott
[not found] <3SAEx-7Yo-9@gated-at.bofh.it>
2005-04-12 23:21 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-04-13 7:27 ` Christoph Hellwig
2005-04-12 21:46 Kilau, Scott
2005-04-12 22:28 ` Matt Mackall
2005-04-12 20:21 Kilau, Scott
2005-04-12 21:32 ` Matt Mackall
2005-04-12 21:42 ` Greg KH
2005-04-12 20:01 Kilau, Scott
2005-04-12 16:54 Kilau, Scott
2005-04-12 17:30 ` Greg KH
2005-04-12 16:42 Kilau, Scott
2005-04-12 18:48 ` Jan-Benedict Glaw
2005-04-12 15:55 Kilau, Scott
2005-04-12 14:55 Kilau, Scott
2005-04-12 15:13 ` Christoph Hellwig
2005-04-12 14:02 Kilau, Scott
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 12:13 Ihalainen Nickolay
2005-04-12 14:44 ` Christoph Hellwig
2005-04-12 15:38 ` Ihalainen Nickolay
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=20050413072646.GA32634@infradead.org \
--to=hch@infradead.org \
--cc=Scott_Kilau@digi.com \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wendyx@us.ibm.com \
/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