From: Stephen Hemminger <stephen@networkplumber.org>
To: Carl Bordum Hansen <carl@bordum.dk>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ip link docs: mention wireguard interface type
Date: Wed, 9 Jun 2021 17:22:49 -0700 [thread overview]
Message-ID: <20210609172249.6eb3b05d@hermes.local> (raw)
In-Reply-To: <20210604230534.104899-1-carl@bordum.dk>
On Sat, 5 Jun 2021 01:05:34 +0200
Carl Bordum Hansen <carl@bordum.dk> wrote:
> Signed-off-by: Carl Bordum Hansen <carl@bordum.dk>
> ---
> ip/iplink.c | 2 +-
> man/man8/ip-link.8.in | 6 +++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/ip/iplink.c b/ip/iplink.c
> index 27c9be44..d676a8de 100644
> --- a/ip/iplink.c
> +++ b/ip/iplink.c
> @@ -123,7 +123,7 @@ void iplink_usage(void)
> " gre | gretap | erspan | ip6gre | ip6gretap | ip6erspan |\n"
> " vti | nlmon | team_slave | bond_slave | bridge_slave |\n"
> " ipvlan | ipvtap | geneve | bareudp | vrf | macsec | netdevsim | rmnet |\n"
> - " xfrm }\n");
> + " xfrm | wireguard }\n");
That part of the code has changed recently on main branch, your change no longer applies.
> }
> exit(-1);
> }
> diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
> index fd67e611..6fbd5bf4 100644
> --- a/man/man8/ip-link.8.in
> +++ b/man/man8/ip-link.8.in
> @@ -231,7 +231,8 @@ ip-link \- network device configuration
> .BR macsec " |"
> .BR netdevsim " |"
> .BR rmnet " |"
> -.BR xfrm " ]"
> +.BR xfrm " |"
> +.BR wireguard " ]"
List should be alphabetical
>
> .ti -8
> .IR ETYPE " := [ " TYPE " |"
> @@ -377,6 +378,9 @@ Link types:
> .sp
> .BR xfrm
> - Virtual xfrm interface
> +.sp
> +.BR wireguard
> +- Wireguard interface
> .in -8
>
> .TP
prev parent reply other threads:[~2021-06-10 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 23:05 [PATCH] ip link docs: mention wireguard interface type Carl Bordum Hansen
2021-06-10 0:22 ` Stephen Hemminger [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=20210609172249.6eb3b05d@hermes.local \
--to=stephen@networkplumber.org \
--cc=carl@bordum.dk \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).