All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Pali Rohár" <pali@kernel.org>,
	"Michael Kerrisk" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] netlink.7: Fix minimal Linux version for NETLINK_CAP_ACK
Date: Sun, 10 Jan 2021 15:49:50 +0100	[thread overview]
Message-ID: <880e9bdd-9046-a7eb-4d21-697b56cb1d7e@gmail.com> (raw)
In-Reply-To: <20210110140027.14937-1-pali@kernel.org>

On 1/10/21 3:00 PM, Pali Rohár wrote:
> NETLINK_CAP_ACK option was introduced in commit 0a6a3a23ea6e which first
> appeared in Linux version 4.3 and not 4.2.
> 
> Signed-off-by: Pali Rohár <pali@kernel.org>

Hi Pali, patch applied.

Thanks,

Alex

> ---
>  man7/netlink.7 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man7/netlink.7 b/man7/netlink.7
> index b14e981d1..ec5d0e71f 100644
> --- a/man7/netlink.7
> +++ b/man7/netlink.7
> @@ -491,7 +491,7 @@ The
>  .I nsid
>  is sent to user space via an ancillary data.
>  .TP
> -.BR NETLINK_CAP_ACK " (since Linux 4.2)"
> +.BR NETLINK_CAP_ACK " (since Linux 4.3)"
>  .\"	commit 0a6a3a23ea6efde079a5b77688541a98bf202721
>  .\"	Author: Christophe Ricard <christophe.ricard@gmail.com>
>  The kernel may fail to allocate the necessary room for the acknowledgment
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-01-10 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 14:00 [PATCH] netlink.7: Fix minimal Linux version for NETLINK_CAP_ACK Pali Rohár
2021-01-10 14:49 ` Alejandro Colomar (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-16 15:06 Alejandro Colomar
2021-01-17 20:43 ` 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=880e9bdd-9046-a7eb-4d21-697b56cb1d7e@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=pali@kernel.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.