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: Re: [PATCH] cifs-utils: mention the required kernel version to make cifs.idmap work
Date: Mon, 17 Oct 2011 17:46:40 +0530 [thread overview]
Message-ID: <4E9C1CA8.7040105@suse.de> (raw)
In-Reply-To: <20111017081139.564089db-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On 10/17/2011 05:41 PM, Jeff Layton wrote:
> On Mon, 17 Oct 2011 17:33:47 +0530
> Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
>
>> .. properly in the "NOTES" section.
>>
>> Cc: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
>> ---
>> cifs.idmap.8.in | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/cifs.idmap.8.in b/cifs.idmap.8.in
>> index f2fa3b2..7adfdc6 100644
>> --- a/cifs.idmap.8.in
>> +++ b/cifs.idmap.8.in
>> @@ -76,6 +76,9 @@ create cifs\&.idmap * * @sbindir@/cifs\&.idmap %k
>> See
>> \fBrequest-key.conf\fR(5)
>> for more info on each field\&.
>> +.SH "NOTES"
>> +.PP
>> +For cifs.idmap to work properly you would need a kernel version 3.0 or above.
>> .SH "SEE ALSO"
>> .PP
>>
>
> This looks reasonable, but I'm always a bit leery of calling out
> specific versions like this. Some distros (e.g. Red Hat's and Novell's)
> will backport features from later kernels, so saying you need a 3.0
> kernel might be confusing.
>
> We might want to rephrase this with something like "Support for upcalls
> to cifs.idmap was initially introduced in the 3.0 kernel." It's a
> little more weaselly but it isn't false if someone is working with a
> kernel that has backported this code.
>
> Sound reasonable?
Yes. Also, I'd like to get Shirish Ack (just to be sure) before this one
gets merged.
I'll repost it.
Suresh
next prev parent reply other threads:[~2011-10-17 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 12:03 [PATCH] cifs-utils: mention the required kernel version to make cifs.idmap work Suresh Jayaraman
[not found] ` <4E9C19A3.8010009-l3A5Bk7waGM@public.gmane.org>
2011-10-17 12:11 ` Jeff Layton
[not found] ` <20111017081139.564089db-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-10-17 12:16 ` Suresh Jayaraman [this message]
2011-10-17 16:59 ` Steve French
[not found] ` <CAH2r5msxArv-Hdy6sBVGbNtLcjhwk0EUwGj07H85iOT4KHqiRg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-17 17:06 ` Jeff Layton
[not found] ` <20111017130654.53fd42c4-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-10-17 17:33 ` Steve French
2011-10-18 6:07 ` Suresh Jayaraman
[not found] ` <4E9D17AA.8020407-l3A5Bk7waGM@public.gmane.org>
2011-10-21 3:29 ` Steve French
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=4E9C1CA8.7040105@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.