All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Marco Bonelli <marco@mebeim.net>, linux-man@vger.kernel.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] proc.5: Document KPF_PGTABLE for /proc/kpageflags
Date: Fri, 31 Mar 2023 02:09:35 +0200	[thread overview]
Message-ID: <7c021544-e661-72ce-e359-1f2c658e16be@gmail.com> (raw)
In-Reply-To: <20220617122244.3402528-1-marco@mebeim.net>


[-- Attachment #1.1: Type: text/plain, Size: 1021 bytes --]

Hello Marco,

On 6/17/22 14:22, Marco Bonelli wrote:
> KPG_PGTABLE (bit 26) was introduced in Linux v4.18 (commit
> 1d40a5ea01d53251c23c7be541d3f4a656cfc537).
> 
> Signed-off-by: Marco Bonelli <marco@mebeim.net>

With some delay... patch applied :)

Thanks!
Alex

> ---
>  man5/proc.5 | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/man5/proc.5 b/man5/proc.5
> index 7ceb6d5..1115101 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -3358,6 +3358,8 @@ The bits are as follows:
>  .\" KPF_ZERO_PAGE: commit 56873f43abdcd574b25105867a990f067747b2f4
>      25 - KPF_IDLE           (since Linux 4.3)
>  .\" KPF_IDLE: commit f074a8f49eb87cde95ac9d040ad5e7ea4f029738
> +    26 - KPF_PGTABLE        (since Linux 4.18)
> +.\" KPF_PGTABLE: commit 1d40a5ea01d53251c23c7be541d3f4a656cfc537
>  .IP
>  For further details on the meanings of these bits,
>  see the kernel source file

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-03-31  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 12:22 [PATCH] proc.5: Document KPF_PGTABLE for /proc/kpageflags Marco Bonelli
2023-03-31  0:09 ` Alejandro Colomar [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=7c021544-e661-72ce-e359-1f2c658e16be@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=marco@mebeim.net \
    --cc=mtk.manpages@gmail.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.