From: Roland Dreier <rdreier@cisco.com>
To: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
Cc: fenkes@de.ibm.com, OF-EWG <ewg@lists.openfabrics.org>,
LKML <linux-kernel@vger.kernel.org>,
LinuxPPC-Dev <linuxppc-dev@ozlabs.org>,
raisch@de.ibm.com, alexschm@de.ibm.com,
stefan.roscher@de.ibm.com
Subject: Re: [PATCH] IB/ehca: replace modulus operations in flush error completion path
Date: Fri, 05 Dec 2008 11:25:49 -0800 [thread overview]
Message-ID: <adaabba77b6.fsf@cisco.com> (raw)
In-Reply-To: <200812021631.58810.ossrosch@linux.vnet.ibm.com> (Stefan Roscher's message of "Tue, 2 Dec 2008 16:31:56 +0100")
thanks, applied
prev parent reply other threads:[~2008-12-05 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:31 [PATCH] IB/ehca: replace modulus operations in flush error completion path Stefan Roscher
2008-12-05 19:25 ` Roland Dreier [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=adaabba77b6.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=alexschm@de.ibm.com \
--cc=ewg@lists.openfabrics.org \
--cc=fenkes@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ossrosch@linux.vnet.ibm.com \
--cc=raisch@de.ibm.com \
--cc=stefan.roscher@de.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).