From: Andrea Arcangeli <aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Mike Rapoport <rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] New page describing userfaultfd(2) system call.
Date: Thu, 29 Dec 2016 14:22:15 +0100 [thread overview]
Message-ID: <20161229132215.GA6984@redhat.com> (raw)
In-Reply-To: <1482995717-27063-1-git-send-email-rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Hello,
On Thu, Dec 29, 2016 at 09:15:17AM +0200, Mike Rapoport wrote:
> +.in +4n
> +.nf
> +struct uffdio_copy {
> + __u64 dst;
> + __u64 src;
> + __u64 len;
> + __u64 mode;
> + __s64 copy;
> +};
> +.nf
-.nf
> +.fi
+.in
> +.in +4n
> +.nf
> +struct uffdio_zeropage {
> + struct uffdio_range range;
> + __u64 mode;
> + __s64 zeropage;
> +};
> +.nf
-.nf
> +.fi
+.in
The block opening/closing around the uffdio_copy/zeropage structs
looks more correct in the previous ioctl descriptions so the next line
that follows isn't indented.
Reviewed-by: Andrea Arcangeli <aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
--
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:[~2016-12-29 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 7:15 [PATCH v2] New page describing userfaultfd(2) system call Mike Rapoport
[not found] ` <1482995717-27063-1-git-send-email-rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-12-29 13:22 ` Andrea Arcangeli [this message]
[not found] ` <20161229132215.GA6984-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-29 20:02 ` Michael Kerrisk (man-pages)
2016-12-29 15:08 ` Michael Kerrisk (man-pages)
[not found] ` <3ffbeecb-03b7-eb00-37e2-9899e14f58ec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-20 9:23 ` Mike Rapoport
2017-03-20 15:11 ` Mike Rapoport
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=20161229132215.GA6984@redhat.com \
--to=aarcange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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.