My point is to respect musl-libc changes and patch iproute2 as how we
patch kernel.
I take two patches[0] from generic kernel patch dir and change glibc
check to libc check.
If you have any interest, you can check mine[1], it is based on iproute2 4.7.0
[0]:
On 19 March 2017 at 14:19, Russell Senior wrote:
>> "Yousong" == Yousong Zhou writes:
>
> Florian> On 03/17/2017 09:51 PM, Yousong Zhou wrote:
> The bug appeared in v4.1.0 and was fixed since v4.8.0
>
> Fixes FS#620
>
>
> "Yousong" == Yousong Zhou writes:
Florian> On 03/17/2017 09:51 PM, Yousong Zhou wrote:
The bug appeared in v4.1.0 and was fixed since v4.8.0
Fixes FS#620
Signed-off-by: Yousong Zhou
Florian> Is there a reason not to
On 19 March 2017 at 07:41, Russell Senior wrote:
>> "Florian" == Florian Fainelli writes:
>
> Florian> On 03/17/2017 09:51 PM, Yousong Zhou wrote:
>>> The bug appeared in v4.1.0 and was fixed since v4.8.0
>>>
>>> Fixes FS#620
>>>
>>>
> "Florian" == Florian Fainelli writes:
Florian> On 03/17/2017 09:51 PM, Yousong Zhou wrote:
>> The bug appeared in v4.1.0 and was fixed since v4.8.0
>>
>> Fixes FS#620
>>
>> Signed-off-by: Yousong Zhou
Florian> Is there a reason not to
On 03/17/2017 09:51 PM, Yousong Zhou wrote:
> The bug appeared in v4.1.0 and was fixed since v4.8.0
>
> Fixes FS#620
>
> Signed-off-by: Yousong Zhou
Is there a reason not to upgrade to a newer iproute2 then? Maybe not for
the 17.01 branch but for the master branch