On Tue, Oct 18, 2011 at 1:36 AM, Suresh Jayaraman <sjayaraman@xxxxxxx> wrote: > > Cc: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx> > Signed-off-by: Suresh Jayaraman <sjayaraman@xxxxxxx> > --- > setcifsacl.8.in | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/setcifsacl.8.in b/setcifsacl.8.in > index 98ab0ac..a18b3de 100644 > --- a/setcifsacl.8.in > +++ b/setcifsacl.8.in > @@ -68,6 +68,9 @@ type: ALLOWED (0x0), DENIED (0x1), OBJECT_ALLOWED (0x5), OBJECT_DENIED (0x6) > flags: OBJECT_INHERIT_FLAG (OI or 0x1), CONTAINER_INHERIT_FLAG (CI or 0x2), NO_PROPAGATE_INHERIT_FLAG (NI or 0x4), INHERIT_ONLY_FLAG (IO or 0x8), INHERITED_ACE_FLAG (IA or 0x10) or a combination/OR of these values. > .PP > mask: Either one of FULL, CHANGE, READ, a combination of R W X D P O, or a hex value > +.SH "NOTES" > +.PP > +Kernel support for getcifsacl/setcifsacl utilities was initially introduced in the 2.6.37 kernel. > .SH "SEE ALSO" Looks fine. Just a nitpicking, since this is a setcifsacl manpage, does getcifsacl also need to be mentioned here? Reviewed-by: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx> > .PP > \fBmount.cifs\fR(8), > -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
