From: Christoph Hellwig <hch@infradead.org>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ihalainen Nickolay <ihanic@dev.ehouse.ru>,
admin@list.net.ru, linux-kernel@vger.kernel.org,
Wen Xiong <wendyx@us.ibm.com>
Subject: Re: Digi Neo 8: linux-2.6.12_r2 jsm driver
Date: Tue, 12 Apr 2005 16:13:32 +0100 [thread overview]
Message-ID: <20050412151332.GA10752@infradead.org> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F038FBB@mtk-sms-mail01.digi.com>
On Tue, Apr 12, 2005 at 09:55:10AM -0500, Kilau, Scott wrote:
> We (Digi) cares.
>
> We want people to use our DGNC driver over the JSM driver in all
> cases except the 2 port model of the board.
And we (kernel developers) don't care what drivers digi wants people
to use. We empower people to use free software with whatever hardware
can be supported. Our drivers are often not from vendors at all, and
even when vendor drivers exist we often support better (in our opinion)
drivers
>
> This is because the DGNC driver contains extra features that the JSM
> driver
> Has stripped out, to get into the kernel sources,
> and our other customers WANT these features!
There are people who just want the card supported. There's no reason
to deny the driver to them.
> We cannot have a situation where the JSM driver takes control of the PCI
> card
> before the DGNC driver can take it first!
Sure, we can have the situation easily. If you want us to care for your
other driver make sure it's submitted for kernel inclusion.
> Please, do *NOT* add this patch!!!
>
> Do I, as a copyright holder on the code in question, have any rights at
> all,
> or are you just going to trample over my wishes, in your zeal?
You do have lots of rights. But as you put the code under the GPL we
do have rights aswell now, and one of the most important rights you gave
us is to modify and redistribute the code under the terms of the GPL.
next prev parent reply other threads:[~2005-04-12 15:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 14:55 Digi Neo 8: linux-2.6.12_r2 jsm driver Kilau, Scott
2005-04-12 15:13 ` Christoph Hellwig [this message]
-- 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 15:30 Kilau, Scott
2005-04-12 15:32 ` Christoph Hellwig
2005-04-13 3:27 ` Ricky Beam
2005-04-13 7:26 ` Christoph Hellwig
2005-04-12 16:16 ` Greg KH
2005-04-12 16:23 ` Jan-Benedict Glaw
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=20050412151332.GA10752@infradead.org \
--to=hch@infradead.org \
--cc=Scott_Kilau@digi.com \
--cc=admin@list.net.ru \
--cc=ihanic@dev.ehouse.ru \
--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