linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
Cc: LinuxPPC-Dev <linuxppc-dev@ozlabs.org>,
	fenkes@de.ibm.com, LKML <linux-kernel@vger.kernel.org>,
	raisch@de.ibm.com, OF-EWG <ewg@lists.openfabrics.org>
Subject: Re: [ewg] [PATCH] IB/ehca: Change function return types to correct type.
Date: Mon, 05 May 2008 15:51:59 -0700	[thread overview]
Message-ID: <adawsm8z7n4.fsf@cisco.com> (raw)
In-Reply-To: <200805051711.15281.ossrosch@linux.vnet.ibm.com> (Stefan Roscher's message of "Mon, 5 May 2008 17:11:13 +0200")

thanks, applied

      reply	other threads:[~2008-05-05 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 15:11 [PATCH] IB/ehca: Change function return types to correct type Stefan Roscher
2008-05-05 22:51 ` 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=adawsm8z7n4.fsf@cisco.com \
    --to=rdreier@cisco.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 \
    /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).