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>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjjRzVi3qXvKEz7F1kA=YW_Ygp5PA6z6E1Jr-8cy-6J5g@mail.gmail.com>
Date:   Wed, 24 Oct 2018 14:40:03 +0100
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     andy.gross@...aro.org
Cc:     kvalo@....qualcomm.com,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Govind Singh <govinds@...eaurora.org>,
        David Miller <davem@...emloft.net>,
        Andrew Morton <akpm@...ux-foundation.org>,
        netdev@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-wireless@...r.kernel.org, ath10k@...ts.infradead.org,
        jeffrey.t.kirsher@...el.com, niklas.cassel@...aro.org,
        david.brown@...aro.org
Subject: Re: [GIT] Networking

On Wed, Oct 24, 2018 at 2:24 PM Andy Gross <andy.gross@...aro.org> wrote:
>
> Yes this will conflict with Niklas's patch which is part of the 4.20
> pull requests. I would prefer that we revert Linus's and take Niklas's
> unless there is a compelling argument to have it fixed before -rc1.

I have no objection to just reverting my patch when I get the real fix.

I just don't want my tree to have warnings that I see, and that may
hide new warnings coming in when I do my next pull request..

               Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ