From: David Ahern <dsahern-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Arnaldo Carvalho de Melo
<acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] perf_event_open.2: Update description for mmap_data bit
Date: Fri, 15 Nov 2013 09:36:29 -0700 [thread overview]
Message-ID: <52864D8D.9010003@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1311131254380.348-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
On 11/13/13, 10:59 AM, Vince Weaver wrote:
>
> Here's an updated version of the patch that expands the "mmap" definition
> as well as that of "mmap_data". Also some manpage related formatting
> improvements from the original patch.
>
> I'm not really sure how signed-off-by's and other tags work when modifying
> a patch like this so sorry if I mixed that up.
>
I just want the documentation updated as we find holes. I'm fine with
your change.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-15 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1384291959-5329-1-git-send-email-dsahern@gmail.com>
[not found] ` <1384291959-5329-1-git-send-email-dsahern-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-13 17:59 ` [PATCH] perf_event_open.2: Update description for mmap_data bit Vince Weaver
[not found] ` <alpine.DEB.2.10.1311131254380.348-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2013-11-15 16:36 ` David Ahern [this message]
2013-12-12 3:39 ` Michael Kerrisk (man-pages)
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=52864D8D.9010003@gmail.com \
--to=dsahern-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@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.