All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma
	(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: failure to get gid with rdma_bind_addr with >= 3.10 kernels
Date: Sun, 5 Jan 2014 09:25:56 +0200	[thread overview]
Message-ID: <52C90904.2060403@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237388D0FCD0-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>

On 02/01/2014 19:04, Hefty, Sean wrote:
>> Can you please prepare a fresh (gift to 2014) release of librdmacm, such
>> that distributions && people using kernels >= 3.11 will be able to have
>> this functionality restored once they upgrade librdmacm.
> There's a 1.0.17.1 release available with this fix.

good to know... was it announced on the list?


> I will release 1.0.18 within a couple of weeks.

cool
--
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

      parent reply	other threads:[~2014-01-05  7:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <527F6896.1080802@mellanox.com>
     [not found] ` <527F6896.1080802-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-10 11:10   ` failure to get gid with rdma_bind_addr with >= 3.10 kernels Or Gerlitz
     [not found]     ` <527F69B1.9070701-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-10 11:14       ` Or Gerlitz
     [not found]         ` <527F6A8F.1030506-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-11 16:45           ` Hefty, Sean
     [not found]             ` <1828884A29C6694DAF28B7E6B8A8237388CF6F30-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-11 17:09               ` Christoph Lameter
2013-11-11 17:40       ` Hefty, Sean
     [not found]         ` <1828884A29C6694DAF28B7E6B8A8237388CF6F78-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-11 18:14           ` Christoph Lameter
     [not found]             ` <00000142485f86e5-c3027528-9892-4d5c-8d72-0ed5f98666c4-000000-p/GC64/jrecnJqMo6gzdpkEOCMrvLtNR@public.gmane.org>
2013-11-11 18:46               ` Hefty, Sean
     [not found]                 ` <1828884A29C6694DAF28B7E6B8A8237388CF6FD0-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-11 19:41                   ` Christoph Lameter
2013-11-12  7:08                   ` Or Gerlitz
     [not found]                     ` <5281D3E0.70203-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-11-13 20:15                       ` Hefty, Sean
     [not found]                         ` <1828884A29C6694DAF28B7E6B8A8237388D02FEC-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-11-13 22:38                           ` Or Gerlitz
2014-01-02  9:39                   ` Or Gerlitz
     [not found]                     ` <52C533C0.3070103-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-01-02 15:17                       ` Yann Droneaud
     [not found]                         ` <1388675827.22995.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-01-02 16:33                           ` Hefty, Sean
     [not found]                             ` <1828884A29C6694DAF28B7E6B8A8237388D0FBFA-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-01-02 16:59                               ` Yann Droneaud
2014-01-02 17:04                       ` Hefty, Sean
     [not found]                         ` <1828884A29C6694DAF28B7E6B8A8237388D0FCD0-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-01-05  7:25                           ` Or Gerlitz [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=52C90904.2060403@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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.