From: David Ahern <dsahern@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>, dsahern@kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next 3/4] ip, neigh: Add missing NTF_USE support
Date: Fri, 15 Oct 2021 18:18:37 -0600 [thread overview]
Message-ID: <4e842bc5-116b-66c6-b8dc-487b4b5d15ed@gmail.com> (raw)
In-Reply-To: <20211015225319.2284-4-daniel@iogearbox.net>
On 10/15/21 4:53 PM, Daniel Borkmann wrote:
> diff --git a/ip/ipneigh.c b/ip/ipneigh.c
> index 564e787c..9510e03e 100644
> --- a/ip/ipneigh.c
> +++ b/ip/ipneigh.c
> @@ -51,7 +51,7 @@ static void usage(void)
> fprintf(stderr,
> "Usage: ip neigh { add | del | change | replace }\n"
> " { ADDR [ lladdr LLADDR ] [ nud STATE ] proxy ADDR }\n"
> - " [ dev DEV ] [ router ] [ extern_learn ] [ protocol PROTO ]\n"
> + " [ dev DEV ] [ router ] [ use ] [ extern_learn ] [ protocol PROTO ]\n"
> "\n"
> " ip neigh { show | flush } [ proxy ] [ to PREFIX ] [ dev DEV ] [ nud STATE ]\n"
> " [ vrf NAME ]\n"
does not apply to iproute2-next; looks like you made the change against
main branch.
next prev parent reply other threads:[~2021-10-16 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 22:53 [PATCH iproute2 -next 0/4] ip, neigh: Add managed neighbor support Daniel Borkmann
2021-10-15 22:53 ` [PATCH iproute2 -next 1/4] Update kernel headers Daniel Borkmann
2021-10-15 22:53 ` [PATCH iproute2 -next 2/4] ip, neigh: Fix up spacing in netlink dump Daniel Borkmann
2021-10-15 22:53 ` [PATCH iproute2 -next 3/4] ip, neigh: Add missing NTF_USE support Daniel Borkmann
2021-10-16 0:18 ` David Ahern [this message]
2021-10-25 11:43 ` Daniel Borkmann
2021-10-15 22:53 ` [PATCH iproute2 -next 4/4] ip, neigh: Add NTF_EXT_MANAGED support Daniel Borkmann
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=4e842bc5-116b-66c6-b8dc-487b4b5d15ed@gmail.com \
--to=dsahern@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--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).