From: Matthew Garrett <mjg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Daniel Drake <dsd@laptop.org>,
mingo@redhat.com, tglx@linutronix.de, x86@kernel.org,
linux-kernel@vger.kernel.org, dilinger@queued.net,
pgf@laptop.org
Subject: Re: [PATCH v4] x86, olpc: add debugfs interface for EC commands
Date: Tue, 27 Mar 2012 17:07:14 +0100 [thread overview]
Message-ID: <20120327160714.GA8398@srcf.ucam.org> (raw)
In-Reply-To: <20120326145146.23fde0db.akpm@linux-foundation.org>
On Mon, Mar 26, 2012 at 02:51:46PM -0700, Andrew Morton wrote:
> Well, if a person had any contribution at all, we should seek their
> Signed-off-by:. Otherwise they could say "hey, you admitted using my
> code but I did not authorise its use", or any other range of bad IANAL
> things?
The Certificate of Origin says:
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
If a previous author has given a Signed-off-by then they've clearly
indicated that their code is under an appropriate license and may be
submitted to the kernel. If someone else then takes that code, modifies
it and submits it then there's no obvious reason why we still need the
original Signed-off-by. Giving credit to the original author is
obviously appropriate, but I don't see why we need any more than that.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-03-27 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:07 [PATCH v4] x86, olpc: add debugfs interface for EC commands Daniel Drake
2012-03-26 21:29 ` Andrew Morton
2012-03-26 21:31 ` H. Peter Anvin
2012-03-26 21:51 ` Andrew Morton
2012-03-27 16:07 ` Matthew Garrett [this message]
2012-03-27 16:18 ` Valdis.Kletnieks
2012-03-26 22:13 ` Paul Fox
2012-03-26 22:45 ` Daniel Drake
2012-03-26 22:47 ` H. Peter Anvin
2012-03-26 23:05 ` Andrew Morton
2012-03-26 22:53 ` Andrew Morton
2012-03-26 23:57 ` Andres Salomon
2012-03-26 23:14 ` Ingo Molnar
2012-03-26 23:23 ` Andrew Morton
2012-03-26 23:49 ` Ingo Molnar
2012-03-27 4:37 ` Joe Perches
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=20120327160714.GA8398@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pgf@laptop.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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