From: Carlos O'Donell <carlos@redhat.com>
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>
Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor
Date: Tue, 29 Oct 2019 03:26:00 -0000 [thread overview]
Message-ID: <5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@redhat.com> (raw)
In-Reply-To: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com>
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.
next prev parent reply other threads:[~2019-10-29 3:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 3:22 Zhangxuelei (Derek)
2019-10-29 3:26 ` Carlos O'Donell [this message]
2019-10-30 6:42 ` Yikun Jiang
2019-11-01 12:55 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2019-10-26 13:46 Zhangxuelei (Derek)
2019-10-26 13:22 Zhangxuelei (Derek)
2019-10-26 13:40 ` Carlos O'Donell
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
2019-10-29 14:34 ` Wilco Dijkstra
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=5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@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).