linux-kernel - [GIT PULL] please pull infiniband.git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1328636068-25497-1-git-send-email-roland@kernel.org>
Date:	Tue,  7 Feb 2012 09:34:28 -0800
From:	Roland Dreier <roland@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-rdma@...r.kernel.org, target-devel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] please pull infiniband.git

Hi Linus,

Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git ib-srpt-fixes

This will get a few small cleanups and fixes for the srpt fabric
driver.  The driver is new for 3.3 so it makes sense to get this in
before the first release.

----------------------------------------------------------------
Cleanups and error path fixes for the new SRP (SCSI RDMA protocol) target.

----------------------------------------------------------------
Dan Carpenter (1):
      IB/srpt: Fix ERR_PTR() vs. NULL checking confusion

Jesper Juhl (2):
      IB/srpt: Remove unneeded <linux/version.h> include
      IB/srpt: Don't return freed pointer from srpt_alloc_ioctx_ring()

Roland Dreier (2):
      IB/srpt: Use DEFINE_SPINLOCK()/LIST_HEAD()
      IB/srpt: Use ARRAY_SIZE() instead of open-coding

 drivers/infiniband/ulp/srpt/ib_srpt.c |   17 +++++++----------
 drivers/infiniband/ulp/srpt/ib_srpt.h |    1 -
 2 files changed, 7 insertions(+), 11 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/