All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: InfiniBand/RDMA merge plans for 2.6.33
Date: Tue, 15 Dec 2009 10:34:58 +0200	[thread overview]
Message-ID: <20091215083458.GC10744@mtls03> (raw)
In-Reply-To: <adaocm1csgb.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>

On Mon, Dec 14, 2009 at 10:37:40AM -0800, Roland Dreier wrote:
> 
> Here are a few topics that are not ready in time for the 2.6.33 window
> and will need to wait for 2.6.34 at least:
> 
> 
>  - IBoE.  In principle I think this is starting to get there.  Still
>    want to see better ABI compatibility at least, and also make sure
>    the interface chosen works for both rdmacm and non-rdmacm
>    applications.
> 

Based on this, I am going to send a new patch set, a few days after
2.6.33-rc1 is out.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Eli Cohen <eli@dev.mellanox.co.il>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: InfiniBand/RDMA merge plans for 2.6.33
Date: Tue, 15 Dec 2009 10:34:58 +0200	[thread overview]
Message-ID: <20091215083458.GC10744@mtls03> (raw)
In-Reply-To: <adaocm1csgb.fsf@roland-alpha.cisco.com>

On Mon, Dec 14, 2009 at 10:37:40AM -0800, Roland Dreier wrote:
> 
> Here are a few topics that are not ready in time for the 2.6.33 window
> and will need to wait for 2.6.34 at least:
> 
> 
>  - IBoE.  In principle I think this is starting to get there.  Still
>    want to see better ABI compatibility at least, and also make sure
>    the interface chosen works for both rdmacm and non-rdmacm
>    applications.
> 

Based on this, I am going to send a new patch set, a few days after
2.6.33-rc1 is out.

  parent reply	other threads:[~2009-12-15  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 18:37 InfiniBand/RDMA merge plans for 2.6.33 Roland Dreier
2009-12-14 18:37 ` Roland Dreier
     [not found] ` <adaocm1csgb.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-12-14 20:09   ` Ralph Campbell
2009-12-14 20:09     ` Ralph Campbell
     [not found]     ` <1260821358.19688.296.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
2009-12-16 17:20       ` Roland Dreier
2009-12-16 17:20         ` Roland Dreier
2009-12-15  8:34   ` Eli Cohen [this message]
2009-12-15  8:34     ` Eli Cohen
2009-12-16  5:54     ` Or Gerlitz
2009-12-16  5:54       ` Or Gerlitz
2009-12-16  9:03   ` Tziporet Koren
2009-12-16  9:03     ` Tziporet Koren
     [not found]     ` <4B28A259.3040909-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2009-12-16 17:15       ` Roland Dreier
2009-12-16 17:15         ` Roland Dreier

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=20091215083458.GC10744@mtls03 \
    --to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.