From: Greg KH <greg@kroah.com>
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 14:42:57 -0700 [thread overview]
Message-ID: <20050412214256.GA18710@kroah.com> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F122163@mtk-sms-mail01.digi.com>
On Tue, Apr 12, 2005 at 03:21:15PM -0500, Kilau, Scott wrote:
>
> However, neither IBM nor Digi wants this thread's patch to be applied,
> and yet Christoph wants to do it, completely out of spite, to break our
> out-of-tree open source driver.
>
> This is the problem that I have.
But that patch will enable the stock kernel.org kernel to work just fine
for that new device, right? What is wrong with that for all of the
thousands of users of such kernels. And if you want to provide a driver
that works with different features, there's no problem with that either.
We have numerous drivers in the stock kernel tree that work for the same
device, it's up to the distros to proper configure it in the manner they
so wish.
The patch does not "break" any other driver, they can both co-exist just
fine.
If you do object, please realize that this topic will come up again and
again and again as users try to patch the driver to work with the
device. Also realize that people can do this dynamically through sysfs
today...
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-12 22:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 20:21 Digi Neo 8: linux-2.6.12_r2 jsm driver Kilau, Scott
2005-04-12 21:32 ` Matt Mackall
2005-04-12 21:42 ` Greg KH [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: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: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=20050412214256.GA18710@kroah.com \
--to=greg@kroah.com \
--cc=Scott_Kilau@digi.com \
--cc=admin@list.net.ru \
--cc=hch@infradead.org \
--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