umount.2: Homogeneous wording, don't recall function name
PATCH 1/1 umount.2: Homogeneous wording, don't recall function name
See:
man2/link.2:An invalid flag value was specified in man2/swapon.2:An invalid flag value was specified in man2/umount.2:An invalid flag value was specified in man2/unlink.2:An invalid flag value was specified in
--- man2/umount.2 | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
man2/umount.2 +1 -2
@@ -137,8 +137,7 @@ or .BR MNT_FORCE . .TP .BR EINVAL " (since Linux 2.6.34)" -.BR umount2 () -was called with an invalid flag value in +An invalid flag value was specified in .IR flags . .TP .B ENAMETOOLONG
Signature · 6 lines
1.8.5.3 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 1393630618-11940-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org
Hi,
Quoted 5 lines · Simon Paillard
See:
man2/link.2:An invalid flag value was specified in man2/swapon.2:An invalid flag value was specified in man2/umount.2:An invalid flag value was specified in man2/unlink.2:An invalid flag value was specified in
Forget this patch, as umount manpage explains both umount() and umount2(), hence the need to explicit which function EINVAL details are about.
Quoted 20 lines
--- man2/umount.2 | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)man2/umount.2 +1
-2@@ -137,8 +137,7 @@ or .BR MNT_FORCE . .TP .BR EINVAL " (since Linux 2.6.34)" -.BR umount2 () -was called with an invalid flag value in +An invalid flag value was specified in .IR flags . .TP .B ENAMETOOLONGSignature · 1 line
1.8.5.3
Signature · 5 lines
Simon Paillard -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · Simon Paillard
Hi,
Quoted 5 lines · Simon Paillard
See:
man2/link.2:An invalid flag value was specified in man2/swapon.2:An invalid flag value was specified in man2/umount.2:An invalid flag value was specified in man2/unlink.2:An invalid flag value was specified inForget this patch, as umount manpage explains both
umount()andumount2(), hence the need to explicit which function EINVAL details are about.
Yup.
Thanks,
Michael
Quoted 21 lines
Quoted 20 lines
--- man2/umount.2 | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)man2/umount.2 +1
-2@@ -137,8 +137,7 @@ or .BR MNT_FORCE . .TP .BR EINVAL " (since Linux 2.6.34)" -.BR umount2 () -was called with an invalid flag value in +An invalid flag value was specified in .IR flags . .TP .B ENAMETOOLONGSignature · 1 line
1.8.5.3
Signature · 7 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html