From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-106442-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 78961 invoked by alias); 30 Oct 2019 06:42:32 -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 78950 invoked by uid 89); 30 Oct 2019 06:42:32 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=companys, employees, company's, Glibc
X-HELO: mail-lj1-f182.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=FdVZ5lzx1pzdRgcC1MKTiVooRVJDEWD7WGzeRdeMnPQ=;
        b=EbFlaNQBZJMtT4mcIAQ7O9jjgxq0yN03iPMzaQD5XhtwpUKX6rHnwJsH18iMg+62VO
         IyyTZr5tS/uon5X5BXcBtOqwFtMDw6j9nqKyj63cuCSJwcFZCiIR8TBWBjCarbkP1jhU
         Vjigzxl78i58rmkrrPaJW3xXlHEB2KT91EtdbREbP/KUZjEHkoNa53BUzm4QNNoG2q6u
         b6JbmW467/DsSZls1GGtCaH9M2AyJtO8CORx29aWOolzuU3CLRiHRH5I+Ogr99/aoTeT
         rGW739y/eRA79Ahiu/xvxd6M2YdA0QyoDr21It56yQOfLJIzt8E85PylS0RmXF5rSX5o
         kJUA==
MIME-Version: 1.0
References: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com>
 <5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@redhat.com>
In-Reply-To: <5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@redhat.com>
From: Yikun Jiang <yikunkero@gmail.com>
Date: Wed, 30 Oct 2019 06:42:00 -0000
Message-ID: <CAArz_dD6q0XGgCboUA08E8ysrneSrxzxvNU5himBYvH6LMj3Aw@mail.gmail.com>
Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: "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>, 
	Wilco Dijkstra <Wilco.Dijkstra@arm.com>, 
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>, jiangyikun <jiangyikun@huawei.com>
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2019-10/txt/msg00905.txt.bz2

Hi, Carlos or someone can reply, : ) Sorry to bother you guys in here.

And @Craig mentioned the corporate copyright assignment from
copyright-clerk@fsf.org, but no more detail information in follow up.

Looks like we have two choice:
a. employer disclaimer + individual assignment
b. corporate assignment

We are employees of Huawei, and we have achieved the company's
approval to contribute the code in GNU Glibc.

and we have already signed the individual assignment with FSF. (Yikun
Jiang(1435635), Xuelei Zhang(1436346)).

Could you tell us which the copyright assignment should we use? What
should we do for the next step?

Regards,
Yikun