From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, Axel Rasmussen <axelrasmussen@google.com>,
Nadav Amit <nadav.amit@gmail.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v5 0/4] man2: udpate mm/userfaultfd manpages to latest
Date: Mon, 5 Apr 2021 13:50:33 +0200 [thread overview]
Message-ID: <09da1b57-14c9-58f4-dd35-0b9aba2d944a@gmail.com> (raw)
In-Reply-To: <76f5d3a7-626e-563b-c1bd-d318a476a8ed@gmail.com>
Hi Alex,
> I applied all 4 patches (with a few minor fixes to 1/4 and 4/4 (cosmetic
> fixes; some of them about the 80-col right margin)):
> <https://github.com/alejandro-colomar/man-pages/tree/eb8f2001d493d458d08b9b87605ed2ac453c7f5f>
How big is your current queue of pending patches from others?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-04-05 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 22:18 [PATCH v5 0/4] man2: udpate mm/userfaultfd manpages to latest Peter Xu
2021-03-29 22:18 ` [PATCH v5 1/4] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-29 22:18 ` [PATCH v5 2/4] userfaultfd.2: Add write-protect mode Peter Xu
2021-03-29 22:18 ` [PATCH v5 3/4] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-29 22:18 ` [PATCH v5 4/4] ioctl_userfaultfd.2: Add write-protect mode docs Peter Xu
2021-04-01 12:00 ` [PATCH v5 0/4] man2: udpate mm/userfaultfd manpages to latest Alejandro Colomar (man-pages)
2021-04-05 11:50 ` Michael Kerrisk (man-pages) [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=09da1b57-14c9-58f4-dd35-0b9aba2d944a@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).