All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: raph@raphnet.net, alessandro.zummo@towertech.it,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add max6902 RTC support
Date: Tue, 30 May 2006 23:55:00 -0700	[thread overview]
Message-ID: <20060530235500.edc9ef49.akpm@osdl.org> (raw)
In-Reply-To: <1149057131.7461.40.camel@localhost.localdomain>

On Wed, 31 May 2006 07:32:11 +0100
Ian Campbell <ijc@hellion.org.uk> wrote:

> On Tue, 2006-05-30 at 15:01 -0700, Andrew Morton wrote:
> > That's a problem.  According to the Developer's Certificate of Origin
> > process we'd need "Someone at Compulab" to send us a Signed-off-by:, along
> > with the assertions which that carries.
> 
> Don't clauses (a) and/or (b) include provisions that mean Raphael takes
> on this responsibility if he believes that CompuLab released the patch
> under a suitable open source license? In particular the "to the best of
> my knowledge, is covered under an appropriate open source license" bit
> in (b).

hm, sometimes it helps to read things.

>         (a) The contribution was created in whole or in part by me and I
>         have the right to submit it under the open source license
>         indicated in the file; or
>         
>         (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

Yes, I think that would work, if Rafael is prepared to make that assertion.

If so, please send along a few words describing where the Compulab code
came from and some substantiation of your belief that it was appropriately
licensed.  (It probably had some license words at the top of the file..)

  reply	other threads:[~2006-05-31  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 15:09 [PATCH] Add max6902 RTC support Raphael Assenat
2006-05-30 18:32 ` Alessandro Zummo
2006-05-30 18:49   ` Raphael Assenat
2006-05-30 22:01     ` Andrew Morton
2006-05-31  6:32       ` Ian Campbell
2006-05-31  6:55         ` Andrew Morton [this message]
2006-05-31 12:43           ` Raphael Assenat
2006-05-31 17:13             ` Andrew Morton
2006-06-02 16:38               ` Raphael Assenat

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=20060530235500.edc9ef49.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=ijc@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raph@raphnet.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.