mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masanori ITOH <marc@labs.fujitsu.com>
To: woody@jf.intel.com, sean.hefty@intel.com, hozer@hozed.org,
	infiniband-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the linux kernel
Date: Wed, 04 Feb 2004 20:26:02 +0900 (JST)	[thread overview]
Message-ID: <20040204.202602.70222883.marc@labs.fujitsu.com> (raw)
In-Reply-To: <F595A0622682C44DBBE0BBA91E56A5ED1C3664@orsmsx410.jf.intel.com>

Hi Robert, Sean,

Message-ID: <F595A0622682C44DBBE0BBA91E56A5ED1C3664@orsmsx410.jf.intel.com>
> Hi Masonori, 
> 
> I think that Sean has already pushed the code changes for 2.6 for 
> complib, IBAL, and SDP.  As I stated before, we have yet to test it on
> 2.6,
> but it should now compile. Let us know if you have any issues.

Currently, it doesn't seem to be available for 'bk pull', but
I will check it out as soon as it becomes public.

http://infiniband.bkbits.net:8080/iba/ChangeSet@-7d?nav=index.html
----
|Linux InfiniBand(tm) Project 
|-----------------------------------------------------------------------------
|ChangeSet Summaries 
|Age      Author   Rev   Comments 
|35 hours ardavis  1.221 878599 SDP fix for faster rejected connect requests.  
|6 days   jlcoffma 1.220 Fix for SourceForge bug number 880274 for build on the Linux 2.6kernel base. 

Thanks and stay tuned, :)
Masanori

---
Masanori ITOH  Grid Computing & Bioinformatics Lab., Fujitsu Labs. LTD.
               e-mail: marc@labs.fujitsu.com
               phone: +81-44-754-2628 (extension: 7112-6227)
               FingerPrint: 55AF C562 E415 FB1A 8A3A  35D1 AB40 8A9D B8B1 99F8


  reply	other threads:[~2004-02-04 11:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 16:45 Woodruff, Robert J
2004-02-04 11:26 ` Masanori ITOH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:16 Woodruff, Robert J
2004-02-05 21:54 ` Greg KH
2004-02-06 23:20   ` Jamie Lokier
2004-02-05 19:44 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 20:16 ` Greg KH
2004-02-05 19:38 [Infiniband-general] Getting an Infiniband access layer in the linux kernel King, Steven R
2004-02-05 21:51 ` Greg KH
2004-02-05 19:31 Raj, Ashok
     [not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 18:34 Raj, Ashok
2004-02-05 18:31 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 18:40 ` Greg KH
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07  2:54 ` Jamie Lokier
     [not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` [Infiniband-general] Getting an Infiniband access layer in the linux kernel Greg KH
2004-02-04  4:53 Woodruff, Robert J
2004-02-04  2:01 Woodruff, Robert J
2004-02-04  4:08 ` Troy Benjegerdes
2004-02-04  0:17 Woodruff, Robert J
2004-02-04  1:03 ` Greg KH
2004-02-02 23:58 Woodruff, Robert J
2004-02-03  0:56 ` Greg KH
2004-02-03  1:38 ` Masanori ITOH
2004-02-03 22:37 ` Troy Benjegerdes

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=20040204.202602.70222883.marc@labs.fujitsu.com \
    --to=marc@labs.fujitsu.com \
    --cc=hozer@hozed.org \
    --cc=infiniband-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.hefty@intel.com \
    --cc=woody@jf.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

all inboxes | Powered by JetHome®