This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC PATCH 0/3] bugfix for aarch64 ILP32
- From: Bamvor Jian Zhang <bamvor dot zhangjian at huawei dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: <libc-alpha at sourceware dot org>, <apinski at cavium dot com>, <yangyingliang at huawei dot com>, <bintian dot wang at huawei dot com>, <dingtianhong at huawei dot com>
- Date: Thu, 19 Mar 2015 12:19:41 +0800
- Subject: Re: [RFC PATCH 0/3] bugfix for aarch64 ILP32
- Authentication-results: sourceware.org; auth=none
- References: <1426674611-26427-1-git-send-email-bamvor dot zhangjian at huawei dot com> <5509A31B dot 3070905 at redhat dot com>
On 2015/3/19 0:08, Carlos O'Donell wrote:
> On 03/18/2015 06:30 AM, Zhang Jian(Bamvor) wrote:
>> This is bamvor from Huawei OS team. We test ILP32 support through
>> LTP testcases for both little endian and big endian. There are some
>> failures we thought they should be fixed in glibc level, so, here they are.
>
> Your changes are legally significant, and will require copyright assignment
> from Huawei. Are you working on getting copyright assignment? I don't presently
> see Huawei assignments for glibc (but I do see them for gcc).
>
> Please review the contribution checklist:
> https://sourceware.org/glibc/wiki/Contribution%20checklist
Hi, Carlos
I do not know the exactly status about this assignment, and I try to collect
the status in huawei. Meanwhile I read the link above. It say "A change of
just a few lines (less than 15 or so) is not legally significant for
copyright." Our patch may be less 15 line because of the second may be
useless according to H,J Lu's suggestion.
Meanwhile, I found that there is not s-o-b in glibc git commit. Should we
remove the s-o-b in my patches as well?
regards
bamvor
[1] http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
> Cheers,
> Carlos.
>
> .
>