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>
Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
Date: Tue, 29 Oct 2019 01:20:00 -0000 [thread overview]
Message-ID: <66ec878b-3544-5d29-4114-32c730412bbd@redhat.com> (raw)
In-Reply-To: <635c9769-27e9-3ae4-81c9-a5921fd0e6b7@redhat.com>
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.
next prev parent reply other threads:[~2019-10-29 1:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 14:25 Zhangxuelei (Derek)
2019-10-22 9:50 ` Yikun Jiang
2019-10-24 14:57 ` Carlos O'Donell
2019-10-26 9:57 ` Florian Weimer
2019-10-26 13:40 ` Carlos O'Donell
2019-10-29 1:20 ` Carlos O'Donell [this message]
2019-10-29 14:34 ` Wilco Dijkstra
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 3:22 Zhangxuelei (Derek)
2019-10-29 3:26 ` Carlos O'Donell
2019-10-30 6:42 ` Yikun Jiang
2019-11-01 12:55 ` Carlos O'Donell
2019-10-26 13:46 Zhangxuelei (Derek)
2019-10-26 13:22 Zhangxuelei (Derek)
2019-10-26 13:40 ` Carlos O'Donell
2019-10-17 13:16 Xuelei Zhang
2019-10-17 14:57 ` Yikun Jiang
2019-10-18 15:50 ` Wilco Dijkstra
2019-10-22 18:29 ` Wilco Dijkstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66ec878b-3544-5d29-4114-32c730412bbd@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=jiangyikun@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=siddhesh@gotplt.org \
--cc=yikunkero@gmail.com \
--cc=zhangxuelei4@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).