[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba39e6d0-c21f-428a-01b1-b923442ef73c@gmail.com>
Date: Thu, 8 Jul 2021 08:46:00 -0600
From: David Ahern <dsahern@...il.com>
To: Roi Dayan <roid@...dia.com>, Hangbin Liu <liuhangbin@...il.com>,
Davide Caratti <dcaratti@...hat.com>
Cc: netdev@...r.kernel.org, Paul Blakey <paulb@...dia.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Roman Mashak <mrv@...atatu.com>,
Baowen Zheng <baowen.zheng@...igine.com>
Subject: Re: [PATCH iproute2-next v4 1/1] police: Add support for json output
On 7/8/21 12:57 AM, Roi Dayan wrote:
>
>
> On 2021-07-07 9:53 AM, Hangbin Liu wrote:
>> On Tue, Jul 06, 2021 at 10:27:34AM +0200, Davide Caratti wrote:
>>> my 2 cents:
>>>
>>> what about using PRINT_FP / PRINT_JSON, so we fix the JSON output
>>> only to show "index", and
>>> preserve the human-readable printout iproute and kselftests? besides
>>> avoiding failures because
>>> of mismatching kselftests / iproute, this would preserve
>>> functionality of scripts that
>>> configure / dump the "police" action. WDYT?
>>
>> +1
>>
>
>
> why not fix the kselftest to look for the correct output?
That is but 1 user. The general rule is that you do not change the
output like you did.
Powered by blists - more mailing lists