This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
- From: Yikun Jiang <yikunkero at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: "Zhangxuelei (Derek)" <zhangxuelei4 at huawei dot com>, Siddhesh Poyarekar <siddhesh at gotplt dot org>, Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>, Florian Weimer <fweimer at redhat dot com>, DJ Delorie <dj at redhat dot com>, Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, jiangyikun <jiangyikun at huawei dot com>
- Date: Wed, 30 Oct 2019 14:42:17 +0800
- Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
- References: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com> <email@example.com>
Hi, Carlos or someone can reply, : ) Sorry to bother you guys in here.
And @Craig mentioned the corporate copyright assignment from
firstname.lastname@example.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?