lkml.org 
[lkml]   [2020]   [May]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: x86/uv cleanups
Date


> On May 5, 2020, at 9:25 AM, Dimitri Sivanich <sivanich@hpe.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@hpe.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(-)

\
 
 \ /
  Last update: 2020-05-05 18:38    [W:2.442 / U:0.308 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site