From: Stephen Hemminger <stephen@networkplumber.org>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] ss: Identify a lot of netlink protocol names
Date: Wed, 29 Oct 2014 22:49:32 -0700 [thread overview]
Message-ID: <20141029224932.0df2edba@urahara> (raw)
In-Reply-To: <1413478018-12373-1-git-send-email-vadim4j@gmail.com>
On Thu, 16 Oct 2014 19:46:58 +0300
Vadim Kochan <vadim4j@gmail.com> wrote:
> There were only few Netlink protocol names:
>
> rtnl, fw, tcpdiag
>
> which were printed on output.
> So added the other ones.
>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
Please make this driven off of a file in /etc/iproute2/ rather than
hard coding a big switch in the code.
next prev parent reply other threads:[~2014-10-30 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 16:46 [PATCH iproute2] ss: Identify a lot of netlink protocol names Vadim Kochan
2014-10-30 5:49 ` Stephen Hemminger [this message]
2014-10-30 15:26 ` vadim4j
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=20141029224932.0df2edba@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.com \
/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).