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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALzJLG9kKW25Z2mQFDx9VNzm-MmqN=J3g=z+xmzogGqNTS=7-g@mail.gmail.com>
Date:   Sun, 24 Dec 2017 13:08:08 +0200
From:   Saeed Mahameed <saeedm@....mellanox.co.il>
To:     David Miller <davem@...emloft.net>
Cc:     Saeed Mahameed <saeedm@...lanox.com>,
        Linux Netdev List <netdev@...r.kernel.org>,
        linux-rdma@...r.kernel.org, Leon Romanovsky <leonro@...lanox.com>,
        Doug Ledford <dledford@...hat.com>
Subject: Re: [pull request][for-next 00/11] Mellanox, mlx5 E-Switch updates 2017-12-19

On Thu, Dec 21, 2017 at 5:03 PM, David Miller <davem@...emloft.net> wrote:
> From: Saeed Mahameed <saeedm@...lanox.com>
> Date: Thu, 21 Dec 2017 06:19:09 +0000
>
>> On Wed, 2017-12-20 at 12:56 -0500, David Miller wrote:
>>> From: Saeed Mahameed <saeedm@...lanox.com>
>>> Date: Tue, 19 Dec 2017 12:33:29 -0800
>>>
>>> > This patchset is based on rc4 and I see that net-next is still on
>>> > rc3, i hope
>>> > this is not a problem.
>>>
>>> If it doesn't pull cleanly into net-next, then it would be a problem.
>>
>> It does pull cleanly.
>
> But if it is based upon rc4 I'll get tons of crap that is non-networking
> related and you should never create a situation like that.
>
> That's not "cleanly"

I see, I will fix that.

Thanks Dave.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ