public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: [git pull] InfiniBand updates
Date: Sun, 08 Jan 2006 14:25:25 -0800	[thread overview]
Message-ID: <adaek3i9x2i.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

The pull will get the following changes:

Dotan Barak:
      IB/mthca: Add support for automatic path migration (APM)

Jack Morgenstein:
      IB/mthca: fix QP size limits for mem-free HCAs
      IB/umad: fix memory leaks
      IB/mthca: fix memory user DB table leak
      IB/mthca: check RDMA limits
      IB/mthca: correct log2 calculation
      IB/mthca: don't change driver's copy of attributes if modify QP fails
      IB/mthca: Fix SRQ cleanup during QP destroy
      IB/mthca: Fix IB_QP_ACCESS_FLAGS handling.
      IB/mthca: Fix corner cases in max_rd_atomic value handling in modify QP
      IB/mthca: fix WQE size calculation in create-srq
      IB/mthca: check return value in mthca_dev_lim call
      IB/mthca: check port validity in modify_qp
      IB/mthca: max_inline_data handling tweaks
      IB/mthca: fix for SQEr-to-RTS transition in modify QP
      IB/mthca: fix for RTR-to-RTS transition in modify QP
      IB/mthca: multiple fixes for multicast group handling
      IB/uverbs: Fix reference counting on error paths
      IB/uverbs: Release event file reference on ib_uverbs_create_cq() error

Michael S. Tsirkin:
      IB/mthca: Fix thinko in mthca_table_find()
      IB/mthca: create_eq with size not a power of 2
      IB/mthca: Fill in vendor_err field in completion with error

Ralph Campbell:
      IB/uverbs: set ah_flags when creating address handle
      IB: Set GIDs correctly in ib_create_ah_from_wc()

Sean Hefty:
      IB/cm: correct reported reject code
      IB/cm: avoid reusing local ID

 drivers/infiniband/core/cm.c                |   16 +-
 drivers/infiniband/core/user_mad.c          |    4 
 drivers/infiniband/core/uverbs_cmd.c        |   21 ++
 drivers/infiniband/core/verbs.c             |    4 
 drivers/infiniband/hw/mthca/mthca_cmd.c     |   12 +
 drivers/infiniband/hw/mthca/mthca_cq.c      |   23 ++
 drivers/infiniband/hw/mthca/mthca_eq.c      |    4 
 drivers/infiniband/hw/mthca/mthca_main.c    |    4 
 drivers/infiniband/hw/mthca/mthca_mcg.c     |   54 ++++--
 drivers/infiniband/hw/mthca/mthca_memfree.c |    4 
 drivers/infiniband/hw/mthca/mthca_qp.c      |  265 +++++++++++++++------------
 drivers/infiniband/hw/mthca/mthca_srq.c     |    2 
 12 files changed, 250 insertions(+), 163 deletions(-)

             reply	other threads:[~2006-01-08 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 22:25 Roland Dreier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-10 23:02 [git pull] InfiniBand updates Roland Dreier
2005-09-11  3:03 ` Chris Wedgwood
2005-09-11  9:00   ` Christoph Hellwig
2005-09-11 15:15   ` 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=adaek3i9x2i.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=torvalds@osdl.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