linux-kernel - [GIT PULL] please pull file locking changes for v3.17

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]

Date:	Mon, 4 Aug 2014 09:22:42 -0400
From:	Jeff Layton <jlayton@...chiereds.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] please pull file locking changes for v3.17

The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:

  Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)

are available in the git repository at:

  git://git.samba.org/jlayton/linux.git tags/locks-v3.17-1

for you to fetch changes up to 73a8f5f7e6350766102fe8fb85048f7f8f0cb5f7:

  locks: purge fl_owner_t from fs/locks.c (2014-07-13 21:39:07 -0400)

----------------------------------------------------------------
(from the branch description for linux-next local branch)

linux-next branch

File locking related changes for v3.17 (pile #1)

Just a couple of changes from Christoph to start us down the road toward
getting rid of the fl_owner_t typedef.

----------------------------------------------------------------
Christoph Hellwig (2):
      locks: typedef fl_owner_t to void *
      locks: purge fl_owner_t from fs/locks.c

 fs/locks.c         | 26 +++++++++++++-------------
 include/linux/fs.h |  2 +-
 2 files changed, 14 insertions(+), 14 deletions(-)

-- 
Jeff Layton <jlayton@...chiereds.net>
--
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/