From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, "Pali Rohár" <pali@kernel.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] netlink.7: Fix minimal Linux version for NETLINK_CAP_ACK
Date: Sun, 17 Jan 2021 21:43:01 +0100 [thread overview]
Message-ID: <32c35a0b-b3de-db4b-d665-d99a5998cee9@gmail.com> (raw)
In-Reply-To: <20210116150600.8001-1-alx.manpages@gmail.com>
Hi Alex and Pali,
On 1/16/21 4:06 PM, Alejandro Colomar wrote:
> From: Pali Rohár <pali@kernel.org>
>
> 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>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks. Patch applied.
Cheers,
Michael
> ---
> 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
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-01-17 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 15:06 [PATCH] netlink.7: Fix minimal Linux version for NETLINK_CAP_ACK Alejandro Colomar
2021-01-17 20:43 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-10 14:00 Pali Rohár
2021-01-10 14:49 ` Alejandro Colomar (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=32c35a0b-b3de-db4b-d665-d99a5998cee9@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox