From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] target: Update copyright ownership to 2012
Date: Sun, 11 Nov 2012 08:56:23 +0000 [thread overview]
Message-ID: <1352624183.6524.26.camel@dabdike> (raw)
In-Reply-To: <1352502014-9782-1-git-send-email-nab@linux-iscsi.org>
On Fri, 2012-11-09 at 23:00 +0000, Nicholas A. Bellinger wrote:
> diff --git a/drivers/target/target_core_alua.c
> b/drivers/target/target_core_alua.c
> index 4c8eea2..035c606 100644
> --- a/drivers/target/target_core_alua.c
> +++ b/drivers/target/target_core_alua.c
> @@ -3,8 +3,9 @@
> *
> * This file contains SPC-3 compliant asymmetric logical unit
> assigntment (ALUA)
> *
> - * Copyright (c) 2009-2010 Rising Tide Systems
> - * Copyright (c) 2009-2010 Linux-iSCSI.org
> + * (c) Copyright 2009-2012 RisingTide Systems LLC.
> + *
> + * Licensed to the Linux Foundation under the General Public License
> (GPL) version 2.
I don't quite understand this last bit. Firstly, I'm not aware of any
agreement with the Linux Foundation over this and secondly one of the
cardinal principles of GPL is the copyleft one that all downstreams get
equal rights, so you can't licence GPL code to anyone in particular
because you have to licence it to everyone. Thirdly, I think it should
be the GNU General Public Licence. In the context of the kernel, that's
probably taken as read, but if you're going to add it explicitly, might
as well be precise.
James
prev parent reply other threads:[~2012-11-11 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 23:00 [PATCH] target: Update copyright ownership to 2012 Nicholas A. Bellinger
2012-11-10 10:15 ` Kirill A. Shutemov
2012-11-10 19:18 ` Pasi Kärkkäinen
2012-11-11 0:18 ` Kyle Moffett
2012-11-11 2:44 ` Nicholas A. Bellinger
2012-11-11 8:56 ` James Bottomley [this message]
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=1352624183.6524.26.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.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;
as well as URLs for NNTP newsgroup(s).