From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Bruce Fields <bfields@fieldses.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: [GIT PULL] file locking changes for v5.16
Date: Fri, 29 Oct 2021 08:55:17 -0400 [thread overview]
Message-ID: <44baecaf3d322ef0674b7b9b88026cf18d371d14.camel@kernel.org> (raw)
The following changes since commit bf9f243f23e6623f310ba03fbb14e10ec3a61290:
Merge tag '5.15-rc-ksmbd-part2' of git://git.samba.org/ksmbd (2021-09-09 16:17:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v5.16
for you to fetch changes up to 482e00075d660a16de822686a4be4f7c0e11e5e2:
fs: remove leftover comments from mandatory locking removal (2021-10-26 12:20:50 -0400)
----------------------------------------------------------------
I know it's a bit early, but I don't expect to take in any more file
locking patches before the merge window opens.
Most of this is just follow-on cleanup work of documentation and
comments from the mandatory locking removal in v5.15. The only real
functional change is that LOCK_MAND flock() support is also being
removed, as it has basically been non-functional since the v2.5 days.
----------------------------------------------------------------
J. Bruce Fields (1):
locks: remove changelog comments
Jeff Layton (3):
locks: remove LOCK_MAND flock lock support
Documentation: remove reference to now removed mandatory-locking doc
fs: remove leftover comments from mandatory locking removal
Mauro Carvalho Chehab (1):
docs: fs: locks.rst: update comment about mandatory file locking
Documentation/filesystems/index.rst | 1 -
Documentation/filesystems/locks.rst | 17 ++----
fs/ceph/locks.c | 3 --
fs/gfs2/file.c | 2 -
fs/locks.c | 161 +++++++++-----------------------------------------------
fs/namei.c | 4 +-
fs/nfs/file.c | 9 ----
fs/read_write.c | 4 --
include/uapi/asm-generic/fcntl.h | 4 ++
9 files changed, 36 insertions(+), 169 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2021-10-29 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 12:55 Jeff Layton [this message]
2021-11-01 17:28 ` [GIT PULL] file locking changes for v5.16 pr-tracker-bot
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=44baecaf3d322ef0674b7b9b88026cf18d371d14.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).