public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Troy Benjegerdes <troy@scl.ameslab.gov>
To: Roland Dreier <roland@topspin.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Fri, 22 Oct 2004 18:59:43 -0500	[thread overview]
Message-ID: <41799EEF.8060902@scl.ameslab.gov> (raw)
In-Reply-To: <52oejbliuk.fsf@topspin.com>

Well, fortunately this has turned out to be a non-issue.

I just went to www.infinibandta.org and the 1.2 spec is available for 
download.

http://www.infinibandta.org/specs/register/publicspec/vol1r1_2.zip
http://www.infinibandta.org/specs/register/publicspec/vol2r1_2.zip

Roland Dreier wrote:

>    Roland> it's orthogonal to any IP issues.  Since the Linux kernel
>    Roland> contains a lot of code written to specs available only
>    Roland> under NDA (and even reverse-engineered code where specs
>    Roland> are completely unavailable), I don't think the expense
>    Roland> should be an issue.
>
>    Francois> One can say good bye to peer review.
>
>Yes and no.  Certainly people without specs can't review spec
>compliance, but review for coding style, locking bugs, etc. is if
>anything more valuable.
>
>Thanks,
>  Roland
>_______________________________________________
>openib-general mailing list
>openib-general@openib.org
>http://openib.org/mailman/listinfo/openib-general
>
>To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>  
>


  reply	other threads:[~2004-10-23  0:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 20:22 InfiniBand incompatible with the Linux kernel? Greg KH
2004-10-08 20:38 ` [openib-general] " Ronald G. Minnich
2004-10-08 22:49 ` Eric W. Biederman
2004-10-08 23:13   ` Greg KH
2004-10-08 23:24     ` Lee Revell
2004-10-08 23:26     ` Dave Jones
2004-10-08 23:29     ` Roland Dreier
2004-10-08 23:13   ` Jeff Garzik
2004-10-08 23:27 ` Roland Dreier
2004-10-08 23:34   ` Greg KH
2004-10-09  3:40     ` Roland Dreier
2004-10-09  0:57   ` Jeff Garzik
2004-10-09  3:09     ` Roland Dreier
2004-10-09  4:23       ` Jeff Garzik
2004-10-09 21:11         ` Roland Dreier
2004-10-10 19:05           ` Alan Cox
2004-10-10 20:33             ` Roland Dreier
2004-10-09 11:50   ` Francois Romieu
2004-10-09 20:47     ` Roland Dreier
2004-10-22 23:59       ` Troy Benjegerdes [this message]
     [not found] ` <6.1.2.0.2.20041008152933.01f671a8@esmail.cup.hp.com>
2004-10-11 18:27   ` Ronald G. Minnich

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=41799EEF.8060902@scl.ameslab.gov \
    --to=troy@scl.ameslab.gov \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=roland@topspin.com \
    --cc=romieu@fr.zoreil.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