From: Roland Dreier <rdreier@cisco.com>
To: "Sean Hefty" <sean.hefty@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 5/6 v2] IB: IP address based RDMA connection manager
Date: Mon, 13 Mar 2006 09:26:43 -0800 [thread overview]
Message-ID: <ada64mife7g.fsf@cisco.com> (raw)
In-Reply-To: <ORSMSX401FRaqbC8wSA0000001e@orsmsx401.amr.corp.intel.com> (Sean Hefty's message of "Mon, 13 Mar 2006 09:11:34 -0800")
Sean> It's dropping the reference on cma_dev, as opposed to
Sean> id_priv.
Duh, sorry.
- R.
next parent reply other threads:[~2006-03-13 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ORSMSX401FRaqbC8wSA0000001e@orsmsx401.amr.corp.intel.com>
2006-03-13 17:26 ` Roland Dreier [this message]
[not found] <ORSMSX401FRaqbC8wSA0000000e@orsmsx401.amr.corp.intel.com>
2006-03-13 15:43 ` [PATCH 5/6 v2] IB: IP address based RDMA connection manager Roland Dreier
2006-03-13 17:11 ` Sean Hefty
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=ada64mife7g.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=sean.hefty@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;
as well as URLs for NNTP newsgroup(s).