From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@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 kernel version that introduced cifs.idmap
Date: Tue, 18 Oct 2011 07:05:46 -0400 [thread overview]
Message-ID: <20111018070546.73bef565@corrin.poochiereds.net> (raw)
In-Reply-To: <4E9C1D74.8010204-IBi9RG/b67k@public.gmane.org>
On Mon, 17 Oct 2011 17:50:04 +0530
Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org> wrote:
> .. 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..a6d9ccb 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
> +Support for upcalls to cifs.idmap was initially introduced in the 3.0
> kernel.
> .SH "SEE ALSO"
> .PP
>
This and the other manpage patches you sent are malformed. Some of the
lines are wrapped. Thunderbird is notorious for doing this. Can you
resend them?
--
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
prev parent reply other threads:[~2011-10-18 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 12:20 [PATCH] cifs-utils: mention the kernel version that introduced cifs.idmap Suresh Jayaraman
[not found] ` <4E9C1D74.8010204-IBi9RG/b67k@public.gmane.org>
2011-10-18 11:05 ` Jeff Layton [this message]
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=20111018070546.73bef565@corrin.poochiereds.net \
--to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sjayaraman-IBi9RG/b67k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox