From: Jeff Layton <jlayton@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, bfields@fieldses.org,
matthew@wil.cx
Subject: [GIT PULL] please pull file locking changes for 3.15
Date: Mon, 31 Mar 2014 09:31:20 -0400 [thread overview]
Message-ID: <20140331093120.10aeaba6@tlielax.poochiereds.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
The following changes since commit 29723adee11804b548903ddb1db666cf4a60f60e:
locks: make locks_mandatory_area check for file-private locks (2014-03-31 08:24:43 -0400)
are available in the git repository at:
git://git.samba.org/jlayton/linux.git locks-3.15
for you to fetch changes up to 29723adee11804b548903ddb1db666cf4a60f60e:
locks: make locks_mandatory_area check for file-private locks (2014-03-31 08:24:43 -0400)
----------------------------------------------------------------
(from the branch description for locks-3.15 local branch)
file locking patches for 3.15
----------------------------------------------------------------
Highlights:
- maintainership change for fs/locks.c. Willy's not interested in
maintaining it these days, and is OK with Bruce and I taking it.
- fix for open vs. setlease race that Al ID'ed
- cleanup and consolidation of file locking code
- eliminate unneeded BUG() call
- merge of file-private lock implementation
--
Jeff Layton <jlayton@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-31 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 13:31 Jeff Layton [this message]
2014-04-04 21:28 ` Linus Torvalds
2014-04-05 0:56 ` Jeff Layton
2014-04-07 1:37 ` Stephen Rothwell
2014-04-07 11:11 ` Jeff Layton
2014-04-07 12:27 ` Stephen Rothwell
2014-04-07 13:35 ` Jeff Layton
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=20140331093120.10aeaba6@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--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
all inboxes | Powered by JetHome®