From: Timothy Miller <miller@techsource.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Rik van Riel <riel@redhat.com>,
Matti Aarnio <matti.aarnio@zmailer.org>, Greg KH <greg@kroah.com>,
Christoph Hellwig <hch@infradead.org>,
"Woodruff, Robert J" <woody@co.intel.com>,
linux-kernel@vger.kernel.org, "Hefty,
Sean" <sean.hefty@intel.com>,
"Coffman, Jerrie L" <jerrie.l.coffman@intel.com>,
"Davis, Arlin R" <arlin.r.davis@intel.com>,
marcelo.tosatti@cyclades.com
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: Wed, 25 Feb 2004 14:09:27 -0500 [thread overview]
Message-ID: <403CF2E7.4020303@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402251003440.2461@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Wed, 25 Feb 2004, Sam Ravnborg wrote:
>
>>If we take the vendor persåective here. Then why should they make their
>>driver open source, when the middle layer is not part of the
>>main stream kernel?
>
>
> And why should we take the vendor perspective?
>
> We don't add drivers for stuff that doesn't exist, and is not even likely
> to be used much. That way, when problems occur (and they _will_ occur),
> the burden of the crap will be firmly on the shoulders of the people who
> should care.
I was not suggesting that we add drivers or even the middle layer to the
mainline kernel until there is some use for it. Rather, it wouldn't be
a bad idea for someone to DEVELOP it as a patch which could be mainlined
the moment there became a demand for it. This also leaves the work in
the hands of those who should care, because anyone using the middle
layer has the 'disadvantage' of using a non-standard patch which they
have to take responsibility for using.
next prev parent reply other threads:[~2004-02-25 19:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 19:29 PATCH - InfiniBand Access Layer (IBAL) Woodruff, Robert J
2004-02-24 19:44 ` Greg KH
2004-02-24 19:50 ` Christoph Hellwig
2004-02-24 19:57 ` Greg KH
2004-02-24 22:29 ` Rik van Riel
2004-02-25 0:28 ` Matti Aarnio
2004-02-25 3:39 ` Rik van Riel
2004-02-25 16:25 ` Timothy Miller
2004-02-25 17:34 ` Roland Dreier
2004-02-25 18:55 ` Sam Ravnborg
2004-02-25 18:05 ` Linus Torvalds
2004-02-25 19:09 ` Timothy Miller [this message]
2004-02-25 19:55 ` Sam Ravnborg
2004-02-25 19:05 ` Linus Torvalds
2004-02-25 13:19 ` Christoph Hellwig
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 23:02 Woodruff, Robert J
2004-02-25 3:32 ` Rik van Riel
2004-03-13 22:07 Woodruff, Robert J
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` Greg KH
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
2004-03-14 23:14 Nivedita Singhvi
2004-03-15 22:52 Woodruff, Robert J
2004-03-15 23:17 ` Christoph Hellwig
2004-03-15 23:44 ` Johannes Erdfelt
2004-03-15 23:48 ` Christoph Hellwig
2004-03-15 23:54 ` Johannes Erdfelt
2004-03-16 0:09 ` Christoph Hellwig
2004-03-16 0:18 ` Johannes Erdfelt
2004-03-16 1:41 ` Roland Dreier
2004-03-19 18:47 ` Ulrich Drepper
2004-03-19 19:21 ` Fab Tillier
2004-03-19 20:20 ` Ulrich Drepper
2004-03-19 20:47 ` Roland Dreier
2004-03-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16 ` Roland Dreier
2004-03-20 19:15 Acker, Dave
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=403CF2E7.4020303@techsource.com \
--to=miller@techsource.com \
--cc=arlin.r.davis@intel.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jerrie.l.coffman@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=matti.aarnio@zmailer.org \
--cc=riel@redhat.com \
--cc=sam@ravnborg.org \
--cc=sean.hefty@intel.com \
--cc=torvalds@osdl.org \
--cc=woody@co.intel.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;
as well as URLs for NNTP newsgroup(s).