[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AD4CFABB-0621-41B9-B517-4A57FEA1F027@darbyshire-bryant.me.uk>
Date: Thu, 29 Mar 2018 19:33:52 +0000
From: Kevin Darbyshire-Bryant <kevin@...byshire-bryant.me.uk>
To: David Ahern <dsahern@...il.com>
CC: Stephen Hemminger <stephen@...workplumber.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] json_print: fix print_uint with helper type extensions
> On 26 Mar 2018, at 16:03, David Ahern <dsahern@...il.com> wrote:
>
> On 3/18/18 2:40 AM, Kevin Darbyshire-Bryant wrote:
>>
>>
>>> On 16 Mar 2018, at 20:34, Stephen Hemminger <stephen@...workplumber.org> wrote:
>>>>
>>>> print_uint64(PRINT_ANY, "refcnt", "refcnt %" PRIu64 " ", t->tcm_info)
>>>>
>>>> Signed-off-by: Kevin Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>
>>>
>>> I am fine with this. But since there is no code using it yet, it should
>>> go net-next branch.
>>>
>>> Reviewed-by: Stephen Hemminger <stephen@...workplumber.org>
>>
>> Existing code is tripping up over the hidden uint - > uint64_t promotion in print_uint in iproute2 v4.15, that’s how I fell over the issue. Should I split the patch? One fixing the uint->uint64_t and the other offering the explicit type length options.
>>
>> Obviously I now realise that the email header should have iproute2 in it. Learning, slowly :-)
>>
>
> Kevin: I guess you need to split the patch. Extract the bug fix piece
> and send for iproute2; enhancements go to iproute2-next.
Done that - hopefully done it right or at least better.
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists