public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <Brian.Murrell-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: compiling against lustre 1.8.2 kernel
Date: Mon, 17 May 2010 14:10:03 -0400	[thread overview]
Message-ID: <1274119803.396.360.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <AANLkTikwu0pcBUNaxJQvTJdBDi18KpcQiUeyM3d_YhSi-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Mon, 2010-05-17 at 13:32 -0400, Michael Di Domenico wrote: 
> it wouldn't appear so, guess i should have checked that. sorry...  i'm
> little baffled how they can claim it supports ofed 1.4.2 on a
> 2.6.18-146.11.1 kernel if ofed doesn't support a 2.6.18-164.11.1...
> but i digress, that questions for another list...

Indeed, it is, so any followups should be CC'd to
lustre-discuss-aLEFhgZF4x6X6Mz3xDxJMA@public.gmane.org and should likely drop the linux-rdma
list.  Anyone interested in following, can subscribe to lustre-discuss.

But to address the confusion regarding 2.6.18-164.11.1 and the statement
of support for OFED 1.4.2 in the Lustre release notes, the list of
supported OFED releases and supported vendor kernels is not intended to
be a complete and exhaustive matrix.  We can of course, only provide
support where there is upstream support (i.e. intersection).

I have Bcc'd our release manager to have some verbage to that extent
(i.e. that the matrix is not complete) to our future release notes.

Cheers,
b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2010-05-17 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 16:15 compiling against lustre 1.8.2 kernel Michael Di Domenico
     [not found] ` <AANLkTil_7L_cbglOcaHKPRmrrntXew9jwxvSrTkxNcnF-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-17 16:27   ` Brian J. Murrell
     [not found]     ` <1274113630.396.41.camel-lA68w17JHpfIgqYUaR6mlLDks+cytr/Z@public.gmane.org>
2010-05-17 17:32       ` Michael Di Domenico
     [not found]         ` <AANLkTikwu0pcBUNaxJQvTJdBDi18KpcQiUeyM3d_YhSi-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-17 18:10           ` Brian J. Murrell [this message]

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=1274119803.396.360.camel@pc.interlinx.bc.ca \
    --to=brian.murrell-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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