From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-106414-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 84530 invoked by alias); 29 Oct 2019 03:26:36 -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 84293 invoked by uid 89); 29 Oct 2019 03:26:36 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-5.6 required=5.0 tests=AWL,BAYES_00,KAM_MANYTO,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=H*f:sk:8DC571D, H*MI:sk:8DC571D, H*i:sk:8DC571D, @craig
X-HELO: mx1.redhat.com
Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng
 processor
To: "Zhangxuelei (Derek)" <zhangxuelei4@huawei.com>,
 Yikun Jiang <yikunkero@gmail.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: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com>
From: Carlos O'Donell <carlos@redhat.com>
Message-ID: <5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@redhat.com>
Date: Tue, 29 Oct 2019 03:26: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: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-10/txt/msg00877.txt.bz2

On 10/28/19 11:22 PM, Zhangxuelei (Derek) wrote:
> Hi Carlos,
> 
>> 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.
> 
> We have receveid and replied the mail from @Craig, it seems we need request corporate assignment.
> 
> I will sync our results ASAP after @Craig replied.
> 
> Thanks for your attention and reminder.

Thank you very much for the prompt reply to the FSF!

-- 
Cheers,
Carlos.