From: Jiri Pirko <jiri@resnulli.us>
To: David Ahern <dsahern@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Tariq Toukan <tariqt@mellanox.com>,
netdev@vger.kernel.org, ayal@mellanox.com, moshe@mellanox.com,
jiri@mellanox.com
Subject: Re: [PATCH iproute2 0/3] Devlink health reporter's issues
Date: Wed, 18 Dec 2019 15:53:48 +0100 [thread overview]
Message-ID: <20191218145348.GA2209@nanopsycho> (raw)
In-Reply-To: <4a75df49-e3c9-7b67-a0da-94dda9b06465@gmail.com>
Tue, Dec 17, 2019 at 04:08:31PM CET, dsahern@gmail.com wrote:
>On 12/16/19 9:53 PM, Stephen Hemminger wrote:
>> Applied, devlink really needs to get converted to same json
>> library as rest of iproute2.
>
>We have been saying that for too many releases. rdma has fixed its json
>support; devlink needs to the same.
It's under work now, patches are going to be sent soon, hopefully.
>
>Maybe it is time to stop taking patches.
prev parent reply other threads:[~2019-12-18 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:45 [PATCH iproute2 0/3] Devlink health reporter's issues Tariq Toukan
2019-12-11 15:45 ` [PATCH iproute2 1/3] devlink: Print health reporter's dump time-stamp in a helper function Tariq Toukan
2019-12-11 15:45 ` [PATCH iproute2 2/3] devlink: Add a new time-stamp format for health reporter's dump Tariq Toukan
2019-12-11 15:45 ` [PATCH iproute2 3/3] devlink: Fix fmsg nesting in non JSON output Tariq Toukan
2019-12-17 4:53 ` [PATCH iproute2 0/3] Devlink health reporter's issues Stephen Hemminger
2019-12-17 15:08 ` David Ahern
2019-12-17 16:33 ` Stephen Hemminger
2019-12-18 14:53 ` Jiri Pirko [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=20191218145348.GA2209@nanopsycho \
--to=jiri@resnulli.us \
--cc=ayal@mellanox.com \
--cc=dsahern@gmail.com \
--cc=jiri@mellanox.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tariqt@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.