From: Roland Dreier <rdreier@cisco.com>
To: torvalds@linux-foundation.org, akpm@linux-foundation.org
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
general@lists.openfabrics.org
Subject: [ofa-general] [GIT PULL] please pull infiniband.git
Date: Thu, 24 Sep 2009 12:45:12 -0700 [thread overview]
Message-ID: <ada7hvo160n.fsf@cisco.com> (raw)
Linus, please pull from
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This tree is also available from kernel.org mirrors at:
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This will get the batch of RDMA/InfiniBand changes for the 2.6.32
merge window:
The following changes since commit 86d710146fb9975f04c505ec78caa43d227c1018:
Linus Torvalds (1):
Merge git://git.linux-nfs.org/projects/trondmy/nfs-2.6
are available in the git repository at:
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
Eli Cohen (1):
mlx4_core: Pass cache line size to device FW
Jack Morgenstein (1):
IB/mthca: Fix access to freed memory in catastrophic event handling
Julia Lawall (1):
RDMA/nes: Remove duplicate .ndo_set_mac_address field initialization
Moni Shoua (1):
IPoIB: Don't turn on carrier for a non-active port
Roland Dreier (2):
IB/mad: Fix lock-lock-timer deadlock in RMPP code
Merge branches 'ipoib', 'mad', 'mlx4', 'mthca' and 'nes' into for-linus
drivers/infiniband/core/mad_rmpp.c | 17 +++++++++++++----
drivers/infiniband/hw/mthca/mthca_catas.c | 11 ++++++++---
drivers/infiniband/hw/nes/nes_nic.c | 1 -
drivers/infiniband/ulp/ipoib/ipoib_multicast.c | 7 +++++++
drivers/net/mlx4/fw.c | 5 +++++
5 files changed, 33 insertions(+), 8 deletions(-)
reply other threads:[~2009-09-24 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ada7hvo160n.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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