public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] man/man2const/F_[SG]ETDELEG.2const, man/man2/fcntl.2: Document F_SETDELEG and F_GETDELEG
Date: Tue, 20 Jan 2026 16:12:31 +0100	[thread overview]
Message-ID: <aW-awBnQ6RU8o19b@devuan> (raw)
In-Reply-To: <a0916b361406fa52771cf3dd507521fa1cc31d7c.camel@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]

Hi Jeff,

On Tue, Jan 20, 2026 at 09:39:27AM -0500, Jeff Layton wrote:
> On Sun, 2026-01-18 at 16:42 +0100, Alejandro Colomar wrote:
> > From: Jeff Layton <jlayton@kernel.org>
> > 
> > With Linux 6.19, userland will be able to request a delegation on a file
> > or directory.  These new objects act a lot like file leases, but are
> > based on NFSv4 file and directory delegations.
> > 
> > Add new F_GETDELEG and F_SETDELEG manpages to document them.
> > 
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > [alx: minor tweaks]
> > Signed-off-by: Alejandro Colomar <alx@kernel.org>
> > ---
> >  man/man2/fcntl.2                |   5 +
> >  man/man2const/F_GETDELEG.2const | 265 ++++++++++++++++++++++++++++++++
> >  man/man2const/F_SETDELEG.2const |   1 +
> >  3 files changed, 271 insertions(+)
> >  create mode 100644 man/man2const/F_GETDELEG.2const
> >  create mode 100644 man/man2const/F_SETDELEG.2const
> > 

[...]

> > diff --git a/man/man2const/F_GETDELEG.2const b/man/man2const/F_GETDELEG.2const
> > new file mode 100644
> > index 000000000..e4d98feed
> > --- /dev/null
> > +++ b/man/man2const/F_GETDELEG.2const
> > @@ -0,0 +1,265 @@

[...]

> > +.SH NOTES
> > +Delegations were designed to implement NFSv4 delegations for the Linux NFS server.

Do we have a link to the NFSv4 specification of delegations?  It could
be useful, I think.  What do you think?

[...]

> This all looks great to me. Did you need me to make any other changes?

The only remaining doubt is the question above.

> Thanks for doing the cleanup! FWIW:
> 
> Reviewed-by: Jeff Layton <jlayton@kernel.org>

You're welcome!  And thanks!  :-)


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-01-20 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 17:35 [PATCH man-pages v2 0/2] man/man2const: clean up F_GETLEASE and add F_SETDELEG/F_GETDELEG manpages Jeff Layton
2026-01-14 17:35 ` [PATCH man-pages v2 1/2] man/man2const: document the new F_SETDELEG and F_GETDELEG constants Jeff Layton
2026-01-14 17:50   ` G. Branden Robinson
2026-01-14 18:19     ` Alejandro Colomar
2026-01-18 15:40   ` Alejandro Colomar
2026-01-14 17:35 ` [PATCH man-pages v2 2/2] man/man2const: clean up the F_GETLEASE manpage Jeff Layton
2026-01-14 19:48   ` Alejandro Colomar
2026-01-18 15:42 ` [PATCH v3] man/man2const/F_[SG]ETDELEG.2const, man/man2/fcntl.2: Document F_SETDELEG and F_GETDELEG Alejandro Colomar
2026-01-20 14:39   ` Jeff Layton
2026-01-20 15:12     ` Alejandro Colomar [this message]
2026-01-20 15:30       ` Jeff Layton
2026-01-20 15:58         ` Alejandro Colomar
2026-01-23 15:36           ` Alejandro Colomar

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=aW-awBnQ6RU8o19b@devuan \
    --to=alx@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.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