This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]