All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] move_pages.2: mark deprecated E2BIG
Date: Fri, 13 Sep 2019 13:49:37 +0200	[thread overview]
Message-ID: <CAKgNAkh+XhM_LufZ1=7z0Q2O-bFZozGOFkWSuYam=ep+EPqxKQ@mail.gmail.com> (raw)
In-Reply-To: <1567584638-3133-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>

Hello Yang Xu,

On Wed, 4 Sep 2019 at 10:10, Yang Xu <xuyang2018.jy@cn.fujitsu.com> wrote:
>
> E2BIG was removed in 2.6.29, we should mark it as
> deprecated.
>
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> ---
>  man2/move_pages.2 | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man2/move_pages.2 b/man2/move_pages.2
> index dcdedf28a..3370e9e00 100644
> --- a/man2/move_pages.2
> +++ b/man2/move_pages.2
> @@ -168,7 +168,8 @@ to indicate the error.
>  .SH ERRORS
>  .TP
>  .B E2BIG
> -Too many pages to move.
> +Too many pages to move. It was deprecated since 2.6.29.
> +.\" 3140a2273009c01c27d316f35ab76a37e105fdd8
>  .TP
>  .B EACCES
>  .\" FIXME Clarify "current cpuset" in the description of the EACCES error.

Thanks. I applied this patch. I subsequently reworded the text a little to be:

       E2BIG  Too many pages to move.  Since Linux 2.6.29, the kernel  no
              longer generates this error.

Okay?

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2019-09-13 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  8:10 [PATCH] move_pages.2: mark deprecated E2BIG Yang Xu
2019-09-13 11:49 ` 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='CAKgNAkh+XhM_LufZ1=7z0Q2O-bFZozGOFkWSuYam=ep+EPqxKQ@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=xuyang2018.jy@cn.fujitsu.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 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.