From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Samuel <chris@csamuel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Linux Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/3] lib: introduce some memory copy macros and functions
Date: Thu, 02 Sep 2010 14:50:32 +0800 [thread overview]
Message-ID: <4C7F4938.6090202@cn.fujitsu.com> (raw)
In-Reply-To: <4C7F3C60.7000205@csamuel.org>
On Thu, 02 Sep 2010 15:55:44 +1000, Chris Samuel wrote:
> Hiya,
>
> On 02/09/10 15:44, Miao Xie wrote:
>
>> Ok, I will change it.
>
> Did you just change the "2.1" to "2" in your patch, or did you find
> a specifically version 2 licensed version of that code ?
>
> If so, where was that ?
I just change the "2.1" to "2" in your patch, because the orignal code
is LGPL v2.1, LGPL v2.1 permits us to apply the terms of the ordinary
GNU General Public License instead of it.
This is the clause of LGPL v2.1:
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in these
notices.
Once this change is made in a given copy, it is irreversible for that copy,
so the ordinary GNU General Public License applies to all subsequent copies
and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library
into a program that is not a library.
The following is the URL of LGPL v2.1:
http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html
Thanks
Miao
next prev parent reply other threads:[~2010-09-02 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 10:36 [PATCH 1/3] lib: introduce some memory copy macros and functions Miao Xie
2010-09-01 15:25 ` Peter Zijlstra
2010-09-02 5:44 ` Miao Xie
2010-09-02 5:55 ` Chris Samuel
2010-09-02 6:50 ` Miao Xie [this message]
2010-09-02 7:07 ` Chris Samuel
2010-09-02 7:55 ` Peter Zijlstra
2010-09-02 7:57 ` Peter Zijlstra
2010-09-02 8:16 ` chxanders
2010-09-02 8:24 ` Chris Samuel
2010-09-02 8:35 ` chxanders
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=4C7F4938.6090202@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tytso@mit.edu \
/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 NNTP newsgroup(s).