public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Shih-Yuan Lee (FourDollars)" <sylee@canonical.com>
Cc: <patches@eglibc.org>, <libc-ports@sourceware.org>,
	<rex.tsai@canonical.com>, Jesse Sung <jesse.sung@canonical.com>,
	YC Cheng	<yc.cheng@canonical.com>
Subject: Re: [PATCH] ARM: NEON detected memcpy.
Date: Wed, 03 Apr 2013 16:02:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1304031557150.580@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAAT15mMJSHiO5rZ6EAbss79f_t4Qiaryi-qjmw3TwGg4vrg2=A@mail.gmail.com>

On Wed, 3 Apr 2013, Shih-Yuan Lee (FourDollars) wrote:

> Hi Joseph,
> 
> I know there is some legal homework but I don't know how to do it.
> Could you provide more details about how to put such copyright
> assignment (with some real example is better)?

See 
<http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html>.  To 
use anything based on the 2009 work, either Nokia will need to complete a 
corporate copyright assignment for that work, if it is copyright Nokia 
pursuant to whatever employment contract Siarhei Siamashka had with Nokia 
at the time, or Nokia will need to complete an employer disclaimer and 
Siarhei Siamashka will need to complete an individual assignment.  And the 
same applies for anyone else who has made significant contributions to the 
code.

> About raised power consumption and context switch costs, I may be able
> to add some option in configure for the users to decide if they want
> to use this feature or not.
> How do you think?

I suggest raising such a question of configure options for such trade-offs 
more generally on libc-alpha.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2013-04-03 16:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  7:58 Shih-Yuan Lee (FourDollars)
2013-04-03  8:15 ` Will Newton
2013-04-03  9:19   ` Ondřej Bílka
2013-04-03 15:08 ` Joseph S. Myers
2013-04-03 15:48   ` Shih-Yuan Lee (FourDollars)
2013-04-03 16:02     ` Joseph S. Myers [this message]
2013-04-04  3:56       ` Shih-Yuan Lee (FourDollars)
2013-04-03 16:20     ` [Patches] " Ondřej Bílka
2013-04-04  4:15       ` Shih-Yuan Lee (FourDollars)
2013-04-04  6:37         ` Ondřej Bílka
2013-04-08  9:12           ` Will Newton
2013-04-08 10:27             ` Ondřej Bílka
2013-04-09  8:45         ` Richard Earnshaw
2013-04-09  9:05   ` Richard Earnshaw
2013-04-09 12:04     ` Ondřej Bílka
2013-04-09 12:59     ` Carlos O'Donell
2013-04-09 15:00       ` Richard Earnshaw
2013-04-09 15:54         ` Ondřej Bílka
2013-04-09 15:59         ` Carlos O'Donell

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=Pine.LNX.4.64.1304031557150.580@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=jesse.sung@canonical.com \
    --cc=libc-ports@sourceware.org \
    --cc=patches@eglibc.org \
    --cc=rex.tsai@canonical.com \
    --cc=sylee@canonical.com \
    --cc=yc.cheng@canonical.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).