public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: torvalds@linux-foundation.org, akpm@linux-foundation.org
Cc: general@lists.openfabrics.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] please pull infinibang.git
Date: Wed, 14 May 2008 09:33:44 -0700	[thread overview]
Message-ID: <aday76cj15j.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 a fixes for various low-level HW driver issues:

 - nes bugs with LRO module parameter
 - cxgb3 bug in handling flushing on connection teardown
 - ipath miscellaneous issues (kind of big but look like needed fixes)

Pavel Emelyanov (1):
      IB/ipath: Make ipath_portdata work with struct pid * not pid_t

Ralph Campbell (3):
      IB/ipath: Fix RC and UC error handling
      IB/ipath: Fix many locking issues when switching to error state
      IB/ipath: Fix RDMA read response sequence checking

Roland Dreier (2):
      RDMA/nes: Fix up nes_lro_max_aggr module parameter
      IB/ipath: Change ipath_devdata.ipath_sdma_status to be unsigned long

Steve Wise (1):
      RDMA/cxgb3: Wrap the software send queue pointer as needed on flush

 drivers/infiniband/hw/cxgb3/cxio_hal.c        |    4 +-
 drivers/infiniband/hw/ipath/ipath_driver.c    |   20 +-
 drivers/infiniband/hw/ipath/ipath_file_ops.c  |   19 +-
 drivers/infiniband/hw/ipath/ipath_kernel.h    |   10 +-
 drivers/infiniband/hw/ipath/ipath_qp.c        |  237 ++++++++-----------
 drivers/infiniband/hw/ipath/ipath_rc.c        |  285 +++++++++++-----------
 drivers/infiniband/hw/ipath/ipath_ruc.c       |  329 ++++++++++++++----------
 drivers/infiniband/hw/ipath/ipath_uc.c        |   57 +++--
 drivers/infiniband/hw/ipath/ipath_ud.c        |   66 ++++--
 drivers/infiniband/hw/ipath/ipath_user_sdma.h |    2 -
 drivers/infiniband/hw/ipath/ipath_verbs.c     |  176 +++++++++-----
 drivers/infiniband/hw/ipath/ipath_verbs.h     |   64 ++++-
 drivers/infiniband/hw/nes/nes.c               |    4 -
 drivers/infiniband/hw/nes/nes.h               |    1 -
 drivers/infiniband/hw/nes/nes_hw.c            |    6 +-
 15 files changed, 725 insertions(+), 555 deletions(-)

                 reply	other threads:[~2008-05-14 16:33 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=aday76cj15j.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=akpm@linux-foundation.org \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@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