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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 5 May 2020 09:36:46 -0700
From:   Andy Lutomirski <luto@...capital.net>
To:     Dimitri Sivanich <sivanich@....com>
Cc:     Christoph Hellwig <hch@....de>, x86@...nel.org,
        Mike Travis <mike.travis@....com>,
        Russ Anderson <russ.anderson@....com>,
        linux-kernel@...r.kernel.org
Subject: Re: x86/uv cleanups



> On May 5, 2020, at 9:25 AM, Dimitri Sivanich <sivanich@....com> wrote:
> 
> Yes, we do see a need to clean up old code where it exists, but we would like
> to assume this responsibility ourselves in order to ensure functional continuity
> with externally available open-sourced modules that our customers rely on.  This
> code supports current Superdome Flex systems, as well as forthcoming platforms
> based on Intel Cooper Lake and Sapphire Rapids processors.  Some cleanup is
> already being included as part of a forthcoming patchset in support of the
> upcoming Sapphire Rapids platform.
> 

What is “functional continuity”?  How does unused code support anything?

> Nacked-by: Dimitri Sivanich <sivanich@....com>
> 
>> On Mon, May 04, 2020 at 07:15:16PM +0200, Christoph Hellwig wrote:
>> Hi x86 maintainers,
>> 
>> this series removes various exports and sniplets of dead code
>> from the x86/uv code.
>> 
>> Diffstat:
>> 
>>  8 files changed, 21 insertions(+), 111 deletions(-)

Powered by blists - more mailing lists