public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Alexander Duyck <alexander.h.duyck@intel.com>
Cc: joe@perches.com, josh@joshtriplett.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Only flag FSF address, not gnu.org URL
Date: Mon, 06 Jan 2014 15:52:42 -0800	[thread overview]
Message-ID: <52CB41CA.8070508@zytor.com> (raw)
In-Reply-To: <20140106232717.GA22336@kroah.com>

On 01/06/2014 03:27 PM, Greg KH wrote:
> On Mon, Jan 06, 2014 at 03:16:24PM -0800, Alexander Duyck wrote:
>> This change restricts the check for the for the FSF address in the GPL
>> copyright statement so that it only flags the address, not the references to
>> the gnu.org/licenses URL which appear in numerous drivers.
>>
>> So for example this statement will still return an error:
>>   You should have received a copy of the GNU General Public License
>>   along with this program; if not, write to the Free Software
>>   Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
>>
>> However, this statement will not return an error after this patch:
>>   You should have received a copy of the GNU General Public License
>>   along with this program.  If not, see <http://www.gnu.org/licenses/>.
> 
> Why is this paragraph needed?  The kernel does come with a copy of the
> GPL, so it's not an issue for kernel files, right?
> 

(IANAL but...) Presumably some people might be concerned about it
because of either patches on mailing lists or otherwise separate from
the kernel, or if someone pulls individual files out of the kernel tree
for another project.

	-hpa



  reply	other threads:[~2014-01-06 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 23:16 [PATCH] checkpatch: Only flag FSF address, not gnu.org URL Alexander Duyck
2014-01-06 23:27 ` Greg KH
2014-01-06 23:52   ` H. Peter Anvin [this message]
2014-01-06 23:57     ` Alexander Duyck
2014-01-06 23:57 ` Joe Perches

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=52CB41CA.8070508@zytor.com \
    --to=hpa@zytor.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@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