From: "Ondřej Bílka" <neleai@seznam.cz>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Rich Felker <dalias@libc.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
samba-technical@lists.samba.org,
Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>,
Carlos O'Donell <carlos@redhat.com>,
Stefan Metzmacher <metze@samba.org>,
Christoph Hellwig <hch@infradead.org>,
Boaz Harrosh <bharrosh@panasas.com>,
"Alfred M. Szmidt" <ams@gnu.org>
Subject: Re: [v4, resend] fcntl-linux.h: add new definitions and manual updates for open file description locks
Date: Fri, 23 May 2014 17:57:47 +0200 [thread overview]
Message-ID: <20140523155747.GA14101@domone.podge> (raw)
In-Reply-To: <1399124004-5535-1-git-send-email-jlayton@poochiereds.net>
On Sat, May 03, 2014 at 09:33:24AM -0400, Jeff Layton wrote:
> Open file description locks have been merged into the Linux kernel for
> v3.15. Add the appropriate command-value definitions and an update to
> the manual that describes their usage.
>
> ChangeLog:
>
> 2014-04-24 Jeff Layton <jlayton@poochiereds.net>
>
> [BZ#16839]
> * manual/llio.texi: add section about open file description locks
>
> * sysdeps/unix/sysv/linux/bits/fcntl-linux.h:
> (F_OFD_GETLK, F_OFD_SETLK, F_OFD_SETLKW): New macros.
>
manual/examples/ofdlocks.c entry is missing.
Otherwise ok for me, Carlos, Michael do you have additional comments?
next prev parent reply other threads:[~2014-05-23 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:09 [glibc PATCHi v4] fcntl-linux.h: add new definitions and manual updates for open file description locks Jeff Layton
2014-04-24 15:07 ` Michael Kerrisk (man-pages)
2014-04-24 15:11 ` Jeff Layton
2014-04-24 15:34 ` Michael Kerrisk (man-pages)
2014-04-24 15:47 ` Jeff Layton
2014-05-03 13:33 ` [glibc PATCH v4 resend] " Jeff Layton
2014-05-23 15:57 ` Ondřej Bílka [this message]
2014-05-23 16:00 ` [v4, " Jeff Layton
2014-05-24 6:15 ` Michael Kerrisk (man-pages)
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=20140523155747.GA14101@domone.podge \
--to=neleai@seznam.cz \
--cc=ams@gnu.org \
--cc=bharrosh@panasas.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=hch@infradead.org \
--cc=jlayton@poochiereds.net \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metze@samba.org \
--cc=mtk.manpages@gmail.com \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.