From: Stephen Hemminger <stephen@networkplumber.org>
To: Julien Fortin <julien@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com, dsahern@gmail.com
Subject: Re: [PATCH iproute2-next] ip: ipneigh: json: print ndm_flags as boolean attributes
Date: Thu, 26 Dec 2019 09:04:06 -0800 [thread overview]
Message-ID: <20191226090406.00aebbcf@hermes.lan> (raw)
In-Reply-To: <20191226144415.50682-1-julien@cumulusnetworks.com>
On Thu, 26 Dec 2019 15:44:15 +0100
Julien Fortin <julien@cumulusnetworks.com> wrote:
> From: Julien Fortin <julien@cumulusnetworks.com>
>
> Today the following attributes are printed as json "null" attributes
> NTF_ROUTER
> NTF_PROXY
> NTF_EXT_LEARNED
> NTF_OFFLOADED
>
> $ ip -j neigh show
> [
> {
> "dst": "10.0.2.2",
> "dev": "enp0s3",
> "lladdr": "52:54:00:12:35:02",
> "router": null,
> "proxy": null,
> "extern_learn": null,
> "offload": null,
> "state": [
> "REACHABLE"
> ]
> }
> ]
No, this was intentional. Null is a standard method in JSON
to encode an option being present.
next prev parent reply other threads:[~2019-12-26 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 14:44 [PATCH iproute2-next] ip: ipneigh: json: print ndm_flags as boolean attributes Julien Fortin
2019-12-26 17:04 ` Stephen Hemminger [this message]
2019-12-30 17:38 ` David Ahern
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=20191226090406.00aebbcf@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=julien@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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).