From: Roland Dreier <rdreier@cisco.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
general@lists.openfabrics.org
Subject: Re: [PATCH 2.6.26 1/3] RDMA/cxgb3: QP flush fixes
Date: Fri, 02 May 2008 10:58:10 -0700 [thread overview]
Message-ID: <adamyn84mh9.fsf@cisco.com> (raw)
In-Reply-To: <20080502161741.30500.95337.stgit@dell3.ogc.int> (Steve Wise's message of "Fri, 02 May 2008 11:17:41 -0500")
thanks, applied all 3... (1/3 was against a slightly old tree, so I had
to fix up __FUNCTION__ -> __func__ in the context of the diffs)
next prev parent reply other threads:[~2008-05-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 16:17 [PATCH 2.6.26 1/3] RDMA/cxgb3: QP flush fixes Steve Wise
2008-05-02 16:17 ` [PATCH 2.6.26 2/3] RDMA/cxgb3: Silently ignore close reply after abort Steve Wise
2008-05-02 16:17 ` [PATCH 2.6.26 3/3] RDMA/cxgb3: Bump up the mpa connection setup timeout Steve Wise
2008-05-02 17:58 ` Roland Dreier [this message]
2008-05-02 20:16 ` [ofa-general] Re: [PATCH 2.6.26 1/3] RDMA/cxgb3: QP flush fixes Steve Wise
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=adamyn84mh9.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.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).