From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nikos Mavrogiannopoulos <nmav-c5N7Ur/I1ocdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ioctl_list.2: SIOCADDRT accepts in6_rtmsg in INET6 protocol
Date: Sat, 18 Apr 2015 23:07:27 +0200 [thread overview]
Message-ID: <5532C78F.9040502@gmail.com> (raw)
In-Reply-To: <1429185133.443.1.camel-c5N7Ur/I1ocdnm+yROfE0A@public.gmane.org>
Hello Nikos,
On 04/16/2015 01:52 PM, Nikos Mavrogiannopoulos wrote:
>
> Signed-off-by: Nikos Mavrogiannopoulos <nmav-c5N7Ur/I1ocdnm+yROfE0A@public.gmane.org>
Applied. (If you should send more patches, it would be
helpful to cite locations in the kernel source where the
details can be verified.)
Thanks!
Michael
> ---
> man2/ioctl_list.2 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/man2/ioctl_list.2 b/man2/ioctl_list.2
> index ba993a1..1507d3c 100644
> --- a/man2/ioctl_list.2
> +++ b/man2/ioctl_list.2
> @@ -904,6 +904,7 @@ the protocol:
> Most protocols const struct rtentry *
> AX.25 const struct ax25_route *
> NET/ROM const struct nr_route_struct *
> + INET6 const struct in6_rtmsg *
>
> .fi
> .B SIOCGIFCONF
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-18 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 11:52 [PATCH] ioctl_list.2: SIOCADDRT accepts in6_rtmsg in INET6 protocol Nikos Mavrogiannopoulos
[not found] ` <1429185133.443.1.camel-c5N7Ur/I1ocdnm+yROfE0A@public.gmane.org>
2015-04-18 21:07 ` 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=5532C78F.9040502@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nmav-c5N7Ur/I1ocdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).