lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 16 Feb 2021 08:48:24 -0700
From:   David Ahern <dsahern@...il.com>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Stephen Hemminger <stephen@...workplumber.org>,
        Ido Kalir <idok@...dia.com>,
        linux-netdev <netdev@...r.kernel.org>,
        RDMA mailing list <linux-rdma@...r.kernel.org>
Subject: Re: [PATCH iproute2-rc] rdma: Fix statistics bind/unbing argument
 handling

On 2/15/21 11:16 PM, Leon Romanovsky wrote:
> On Mon, Feb 15, 2021 at 06:56:26PM -0700, David Ahern wrote:
>> On 2/14/21 10:40 PM, Leon Romanovsky wrote:
>>> On Sun, Feb 14, 2021 at 08:26:16PM -0700, David Ahern wrote:
>>>> what does iproute2-rc mean?
>>>
>>> Patch target is iproute2.git:
>>> https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/
>>
>> so you are asking them to be committed for the 5.11 release?
> 
> This is a Fix to an existing issue (not theoretical one), so I was under
> impression that it should go to -rc repo and not to -next.

It is assigned to Stephen for iproute2.

> 
> Personally, I don't care to which repo will this fix be applied as long
> as it is applied to one of the two iproute2 official repos.
> 
> Do you have clear guidance when should I send patches to iproute2-rc/iproute2-next?
> 

It's the rc label that needs to be dropped: iproute2 or iproute2-next.
Just like there is net and net-next.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ