On 03/01/2014 03:42 AM, Simon Paillard wrote: > Hi, > > On Sat, Mar 01, 2014 at 12:36:58AM +0100, Simon Paillard wrote: >> 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. Yup. Thanks, Michael >> --- >> man2/umount.2 | 3 +-- >> 1 file changed, 1 insertion(+), 2 deletions(-) >> >> diff --git a/man2/umount.2 b/man2/umount.2 >> index 86fff50..18a87a0 100644 >> --- a/man2/umount.2 >> +++ b/man2/umount.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 >> -- >> 1.8.5.3 > -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html