All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Shirish Pargaonkar
	<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl
Date: Tue, 18 Oct 2011 12:06:13 +0530	[thread overview]
Message-ID: <4E9D1E5D.4020603@suse.de> (raw)


Cc: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
---
 getcifsacl.8.in |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/getcifsacl.8.in b/getcifsacl.8.in
index 02e1355..f79f7ff 100644
--- a/getcifsacl.8.in
+++ b/getcifsacl.8.in
@@ -40,6 +40,9 @@ Print version number and exit\&.
 .RS 4
 Display a security descriptor in raw mode. Values such as type and flags are displayed in hexadecimal format, a SID is not mapped to a name.
 .RE
+.SH "NOTES"
+.PP
+Kernel support for getcifsacl/setcifsacl utilities was initially introduced in the 2.6.37 kernel.
 .SH "SEE ALSO"
 .PP
 \fBmount.cifs\fR(8),

             reply	other threads:[~2011-10-18  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  6:36 Suresh Jayaraman [this message]
     [not found] ` <4E9D1E5D.4020603-l3A5Bk7waGM@public.gmane.org>
2011-10-18  9:35   ` [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl Shirish Pargaonkar
     [not found]     ` <CADT32eLiG_oqKEu6dtEXyH6kepMwGt+G_+5OJTxefO8y85oCHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-18 10:06       ` Suresh Jayaraman

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=4E9D1E5D.4020603@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.