linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Shirley Ma <xma@us.ibm.com>
Cc: Richard Frank <richard.frank@oracle.com>,
	general@lists.openfabrics.org,
	general-bounces@lists.openfabrics.org,
	linux-kernel@vger.kernel.org, rds-devel@oss.oracle.com
Subject: Re: [ofa-general] InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's	in infiniband.git)
Date: Wed, 02 Apr 2008 09:37:53 -0700	[thread overview]
Message-ID: <adar6do1ace.fsf@cisco.com> (raw)
In-Reply-To: <OF1D776305.7E25BAA6-ON8725741F.005B027C-8825741F.002F5161@us.ibm.com> (Shirley Ma's message of "Wed, 2 Apr 2008 09:36:12 -0700")

 > Can the maintainer submit RDS patch for mainline kernel, in 2.6.26 or
 > 2.6.27 window? It's hard for Distros pick this feature without mainline
 > kernel acceptance.

At least as a first order approximation, there is no chance of RDS being
merged for 2.6.26 even if patches appear right this second...

       reply	other threads:[~2008-04-02 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF1D776305.7E25BAA6-ON8725741F.005B027C-8825741F.002F5161@us.ibm.com>
2008-04-02 16:37 ` Roland Dreier [this message]
2008-04-01 20:02 InfiniBand/iWARP/RDMA merge plans for 2.6.26 (what's in infiniband.git) Roland Dreier
2008-04-01 16:55 ` [ofa-general] " Shirley Ma
2008-04-02  7:22 ` Shirley Ma
2008-04-02 15:27   ` Roland Dreier
2008-04-02 17:11     ` Richard Frank
2008-04-02 16:15       ` Roland Dreier
2008-04-02 17:18         ` Richard Frank
2008-04-02 16:26           ` Roland Dreier
2008-04-02 17:28             ` Richard Frank
2008-04-02 17:24         ` Richard Frank
2008-04-02 12:31 ` Tziporet Koren
2008-04-02 16:19   ` Roland Dreier
2008-04-03 11:40     ` Tziporet Koren
2008-04-04 20:26     ` Richard Frank
2008-04-04 19:34       ` Roland Dreier
2008-04-04 22:21         ` Richard Frank
2008-04-04  5:54   ` Or Gerlitz

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=adar6do1ace.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=general-bounces@lists.openfabrics.org \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=richard.frank@oracle.com \
    --cc=xma@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;
as well as URLs for NNTP newsgroup(s).