From: Peter Zijlstra <peterz@infradead.org>
To: miaox@cn.fujitsu.com
Cc: 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 09:57:00 +0200 [thread overview]
Message-ID: <1283414220.2059.1789.camel@laptop> (raw)
In-Reply-To: <1283414119.2059.1785.camel@laptop>
On Thu, 2010-09-02 at 09:55 +0200, Peter Zijlstra wrote:
> On Thu, 2010-09-02 at 13:44 +0800, Miao Xie wrote:
> > On Wed, 01 Sep 2010 17:25:36 +0200, Peter Zijlstra wrote:
> > > On Wed, 2010-09-01 at 18:36 +0800, Miao Xie wrote:
> > >> + * This program is free software; you can redistribute it and/or modify it
> > >> + * under the terms of the GNU General Public License as published by the Free
> > >> + * Software Foundation; either version 2.1 of the License, or (at your option)
> > >> + * any later version.
> > >
> > > The kernel is GPL v2, see COPYING. GPL v2.1 is not a suitable license.
> >
> > Ok, I will change it.
>
> Are you allowed to change it? from what I understand the FSF owns the
> copyright of that code, that least, that's what the preamble I cut away
> implied.
n/m, I should probably have read more inbox before replying.
next prev parent reply other threads:[~2010-09-02 7:57 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
2010-09-02 7:07 ` Chris Samuel
2010-09-02 7:55 ` Peter Zijlstra
2010-09-02 7:57 ` Peter Zijlstra [this message]
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=1283414220.2059.1789.camel@laptop \
--to=peterz@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@redhat.com \
--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).