All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Ezequiel Garcia <elezegarcia@gmail.com>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	gregkh <gregkh@linuxfoundation.org>,
	Ezequiel Garcia <ezequiel@free-electrons.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC/PATCH v2] ubi: Add ubiblock read-write driver
Date: Wed, 12 Dec 2012 11:50:11 -0800	[thread overview]
Message-ID: <50C8DFF3.2000203@am.sony.com> (raw)
In-Reply-To: <50C8BE2D.5090706@free-electrons.com>

On 12/12/2012 09:26 AM, Michael Opdenacker wrote:
> On 12/12/2012 05:35 PM, Ezequiel Garcia wrote:
>> On a second thought and considering this code is originally
>> copyrighted by Free Electrons,
>> I'd guess I need their permission to make a license change (right?).
>>
>> So considering Greg's comments, I'll leave it as it is and let Free
>> Electrons decide.
> 
> OK for GPLv2 only. You have Free Electron's permission.
> 
> Thanks for asking!

I'm not sure if this code is related to the UBI code that
Free Electrons worked on for CELF some time ago or not -- but
CELF's preference (and CE Workgroup's preference also)
for any code contributions to the kernel is GPLv2 only.

Just FYI.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================

  reply	other threads:[~2012-12-12 19:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 12:21 [RFC/PATCH v2] ubi: Add ubiblock read-write driver Ezequiel Garcia
2012-12-12 15:21 ` richard -rw- weinberger
2012-12-12 15:50   ` Gregory CLEMENT
2012-12-12 16:14     ` richard -rw- weinberger
2012-12-12 16:30       ` Greg KH
2012-12-12 16:32         ` richard -rw- weinberger
2012-12-12 16:18   ` Ezequiel Garcia
2012-12-12 16:35     ` Ezequiel Garcia
2012-12-12 17:26       ` Michael Opdenacker
2012-12-12 19:50         ` Tim Bird [this message]
2013-04-18 20:30 ` Mike Frysinger
2013-04-18 20:58   ` Peter Korsgaard
2013-04-19  0:13   ` Ezequiel Garcia
2013-04-19  1:28     ` Mike Frysinger
2013-04-19  7:10       ` Gupta, Pekon
2013-04-19 11:57         ` Mike Frysinger
2013-04-19 12:31           ` Artem Bityutskiy
2013-04-19 12:31             ` Bityutskiy, Artem
2013-04-19 12:53             ` Mike Frysinger
2013-04-19 12:55               ` Matthieu CASTET
2013-04-24 16:27                 ` Mike Frysinger
2013-04-19 12:56               ` Artem Bityutskiy
2013-04-19 15:02             ` Ezequiel Garcia
2013-04-19 17:05             ` Tim Bird
2013-04-20 18:12               ` Brian Norris
2013-05-13  7:44               ` Artem Bityutskiy
2013-04-20  7:50             ` richard -rw- weinberger
2013-05-13  7:49               ` Artem Bityutskiy
2013-05-13  9:23                 ` richard -rw- weinberger
2013-04-19 12:27       ` Ezequiel Garcia
2013-05-13  7:28   ` Artem Bityutskiy

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=50C8DFF3.2000203@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=dedekind1@gmail.com \
    --cc=elezegarcia@gmail.com \
    --cc=ezequiel@free-electrons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=richard.weinberger@gmail.com \
    --cc=thomas.petazzoni@free-electrons.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 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.