From: Alexander Schmidt <alexs@linux.vnet.ibm.com>
To: Roland Dreier <rdreier@cisco.com>,
Linux RDMA <linux-rdma@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Stefan Roscher <stefan.roscher@de.ibm.com>,
Joachim Fenkes <fenkes@de.ibm.com>,
Christoph Raisch <raisch@de.ibm.com>,
Hoang-Nam Nguyen <HNGUYEN@linux.vnet.ibm.com>,
David Wilder <wilder@us.ibm.com>
Subject: [PATCH 0/2] ib/ehca: fixes for -next
Date: Wed, 27 Jan 2010 18:00:35 +0100 [thread overview]
Message-ID: <20100127180035.779b24d1@alex-laptop> (raw)
Hi Roland,
please apply these two patches for your -next tree.
Regards,
Alex
next reply other threads:[~2010-01-27 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 17:00 Alexander Schmidt [this message]
2010-01-27 17:01 ` [PATCH 1/2] ib/ehca: Do not turn off irqs in tasklet context Alexander Schmidt
2010-01-27 17:03 ` [PATCH 2/2] ib/ehca: allow access for ib_query_qp() Alexander Schmidt
2010-02-12 23:25 ` Roland Dreier
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=20100127180035.779b24d1@alex-laptop \
--to=alexs@linux.vnet.ibm.com \
--cc=HNGUYEN@linux.vnet.ibm.com \
--cc=fenkes@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=raisch@de.ibm.com \
--cc=rdreier@cisco.com \
--cc=stefan.roscher@de.ibm.com \
--cc=wilder@us.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