From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-106411-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 97400 invoked by alias); 29 Oct 2019 01:20:02 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 97381 invoked by uid 89); 29 Oct 2019 01:20:02 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,KAM_MANYTO,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=disclaimer, H*r:ip*192.168.1.4, personal
X-HELO: mx1.redhat.com
Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng
 processor
From: Carlos O'Donell <carlos@redhat.com>
To: Yikun Jiang <yikunkero@gmail.com>,
 "Zhangxuelei (Derek)" <zhangxuelei4@huawei.com>,
 Siddhesh Poyarekar <siddhesh@gotplt.org>,
 Szabolcs Nagy <Szabolcs.Nagy@arm.com>, Florian Weimer <fweimer@redhat.com>,
 DJ Delorie <dj@redhat.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
 "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>, nd <nd@arm.com>,
 jiangyikun <jiangyikun@huawei.com>
References: <8DC571DDDE171B4094D3D33E9685917BD87078@DGGEMI529-MBX.china.huawei.com>
 <CAArz_dBe2gcoDsvdoPOzg6TVR5uTXH4+NaCZ+8_xLD+LEwcBSg@mail.gmail.com>
 <635c9769-27e9-3ae4-81c9-a5921fd0e6b7@redhat.com>
Message-ID: <66ec878b-3544-5d29-4114-32c730412bbd@redhat.com>
Date: Tue, 29 Oct 2019 01:20:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <635c9769-27e9-3ae4-81c9-a5921fd0e6b7@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-10/txt/msg00874.txt.bz2

On 10/24/19 10:50 AM, Carlos O'Donell wrote:
> On 10/22/19 5:50 AM, Yikun Jiang wrote:
>>> Finally, we will submit other generic implenments as soon as possible, and it would be good if you could review this two patches firstly:)
>>
>> All patches have been submitted and updated:
>>
>> [1]. [PATCH] aarch64: Optimized implementation of memrchr
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00526.html
>>
>> [2]. [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00522.html
>>
>> [3] [PATCH v2] aarch64: Optimized implementation of memcmp
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00637.html
>>
>> [4] [PATCH v2] aarch64: Optimized implementation of strcpy
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00639.html
>>
>> [5] [PATCH v2] aarch64: Optimized implementation of strnlen
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00640.html
>>
>> [6] [PATCH v2] aarch64: Optimized strlen for strlen_asimd
>> https://sourceware.org/ml/libc-alpha/2019-10/msg00641.html
> 
> What is the current status of Huawei's copyright assignment
> with the FSF?
> 

At present Huawei does not have an employer disclaimer.

If any of this work can be claimed by Huawei then it cannot be
integrated into glibc.

The FSF is following up with Huawei about this. There was some
confusion over exactly what kind of disclaimer, personal vs.
employer, was being requested.

My sincerest apologies for the delay as we sort this out.

-- 
Cheers,
Carlos.