From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Torsten Duwe <duwe@suse.de>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Sandra Loosemore <sandra@codesourcery.com>,
Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
nd@arm.com, Li Bin <huawei.libin@huawei.com>,
Jiri Kosina <jkosina@suse.cz>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Andrew Wafaa <Andrew.Wafaa@arm.com>
Subject: Re: [PATCH v12] add -fpatchable-function-entry=N,M option
Date: Thu, 20 Jul 2017 13:12:00 -0000 [thread overview]
Message-ID: <395ACE66-8EB3-4B4E-A2AC-E8F38EA78D3C@linaro.org> (raw)
In-Reply-To: <20170720120641.GB29907@suse.de>
> On Jul 20, 2017, at 3:06 PM, Torsten Duwe <duwe@suse.de> wrote:
>
> On Thu, Jul 20, 2017 at 01:58:06PM +0300, Maxim Kuvyrkov wrote:
>>> On Jul 17, 2017, at 3:10 PM, Torsten Duwe <duwe@suse.de> wrote:
>>>
>>> What is the next step now? Is anybody going to commit that patch?
>>
>> Torsten, if you prefer I can commit your patch (after bootstrap and a regtest on aarch64-linux-gnu and x86_64-linux-gnu).
>
> Ok, who is going to do that?
I'll do that, np.
>
>> There is one last hurdle to sort out with the FSF copyright assignment. Looking at FSF's list I don't see SuSe's copyright assignment for your contributions to FSF projects, of which GCC is one. You can either request SuSe to file a copyright assignment for you, or, probably simpler, ask one of your SuSe colleagues (Richard B., Jan H.) to commit under their assignment.
>
> From my understanding, it should not make a difference, as the copyright
> owner is identical (SUSE). But I'm not going to argue on legal issues here.
> Let's first see what the test outcome is. Thanks so far!
SuSe/Novell choose to do its assignments per engineer, not for the whole company, so I don't think you are covered as is.
--
Maxim Kuvyrkov
www.linaro.org
next prev parent reply other threads:[~2017-07-20 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:03 [PATCH v11] " Torsten Duwe
2017-07-07 13:58 ` Richard Earnshaw (lists)
2017-07-07 19:30 ` [PATCH v12] " Torsten Duwe
2017-07-17 12:10 ` Torsten Duwe
2017-07-20 10:58 ` Maxim Kuvyrkov
2017-07-20 12:06 ` Torsten Duwe
2017-07-20 13:12 ` Maxim Kuvyrkov [this message]
2017-07-25 7:16 ` Maxim Kuvyrkov
2017-07-25 8:07 ` Torsten Duwe
2017-07-25 13:03 ` Torsten Duwe
2017-07-26 14:16 ` Andreas Schwab
2017-07-26 14:26 ` Torsten Duwe
2017-07-26 14:33 ` Andreas Schwab
2017-07-31 11:47 ` Maxim Kuvyrkov
2017-08-01 10:43 ` Gerald Pfeifer
2017-08-01 10:53 ` Andreas Schwab
2017-08-01 13:03 ` Maxim Kuvyrkov
2017-08-01 13:36 ` Andreas Schwab
2017-08-11 12:42 ` [PATCH] skip patchable_function_entry tests on ia64 Torsten Duwe
2017-08-14 16:50 ` Jim Wilson
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=395ACE66-8EB3-4B4E-A2AC-E8F38EA78D3C@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=Andrew.Wafaa@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=duwe@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=huawei.libin@huawei.com \
--cc=hubicka@ucw.cz \
--cc=jkosina@suse.cz \
--cc=nd@arm.com \
--cc=polacek@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=sandra@codesourcery.com \
--cc=szabolcs.nagy@arm.com \
--cc=takahiro.akashi@linaro.org \
/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).