linux-kernel - [GIT PULL v2] liblockdep fixes for v3.15

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>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 07 Jul 2014 12:26:11 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Ingo Molnar <mingo@...nel.org>
CC:	"S. Lockwood-Childs" <sjl@...t.vctlabs.com>,
	zhangdianfang <zhangdianfang@...wei.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [GIT PULL v2] liblockdep fixes for v3.15

The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:

  Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes

for you to fetch changes up to b10827814e9c81c5a14fb73c5a6e06bd85df3f94:

  tools/liblockdep: Account for bitfield changes in lockdeps lock_acquire (2014-07-07 12:20:16 -0400)

----------------------------------------------------------------
S. Lockwood-Childs (1):
      tools/liblockdep: Account for bitfield changes in lockdeps lock_acquire

Sasha Levin (1):
      tools/liblockdep: Remove debug print left over from development

zhangdianfang (1):
      tools/liblockdep: Fix comparison of a boolean value with a value of 2

 tools/lib/lockdep/include/liblockdep/mutex.h  |  4 ++--
 tools/lib/lockdep/include/liblockdep/rwlock.h |  8 ++++----
 tools/lib/lockdep/preload.c                   | 20 +++++++++-----------
 3 files changed, 15 insertions(+), 17 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/