From: Stephen Hemminger <shemming@brocade.com>
To: Phil Sutter <phil@nwl.cc>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [iproute PATCH 0/2] ip-neighbour: Add missing nud state descriptions
Date: Fri, 4 Mar 2016 15:36:14 -0800 [thread overview]
Message-ID: <20160304153614.0cf366b7@xeon-e3> (raw)
In-Reply-To: <1a9a42073352495c827050fc81483817@HQ1WP-EXMB11.corp.brocade.com>
On Fri, 4 Mar 2016 19:07:19 +0000
Phil Sutter <phil@nwl.cc> wrote:
> The following aims at documenting all nud states 'ip neigh' supports, not just
> the most common ones. This includes describing them in the relevant man page as
> well as extending 'ip neigh help' output.
>
> Phil Sutter (2):
> man: ip-neighbour.8: Document all known nud states
> ipneigh: List all nud states in help output
>
> ip/ipneigh.c | 9 +++++----
> man/man8/ip-neighbour.8 | 22 +++++++++++++++++++++-
> 2 files changed, 26 insertions(+), 5 deletions(-)
>
Applied
next parent reply other threads:[~2016-03-04 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a9a42073352495c827050fc81483817@HQ1WP-EXMB11.corp.brocade.com>
2016-03-04 23:36 ` Stephen Hemminger [this message]
2016-03-04 19:07 [iproute PATCH 0/2] ip-neighbour: Add missing nud state descriptions Phil Sutter
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=20160304153614.0cf366b7@xeon-e3 \
--to=shemming@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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