public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	stable <stable@kernel.org>
Subject: Re: [PATCH 2/4] xilinx_hwicap: remove improper wording in license statement
Date: Wed, 17 Dec 2008 15:45:25 -0800	[thread overview]
Message-ID: <20081217234525.GA16661@suse.de> (raw)
In-Reply-To: <20081217230855.29a26318@lxorguk.ukuu.org.uk>

On Wed, Dec 17, 2008 at 11:08:55PM +0000, Alan Cox wrote:
> On Wed, 17 Dec 2008 11:28:21 -0800
> Greg Kroah-Hartman <gregkh@suse.de> wrote:
> 
> > GPLv2 doesn't allow additional restrictions to be imposed on any
> > code, so this wording needs to be removed from these files.
> 
> You only need to remove the "Use in .. expressly prohibited bit", the
> rest seems like useful relevant information.

As this ended up just being boiler-plate wording from an internal Xilinx
template, and didn't apply at all to these files, it seemed easier to
just remove the whole thing :)

thanks,

greg k-h

  reply	other threads:[~2008-12-17 23:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 19:27 [GIT PATCH] driver core fixes for your 2.6-git tree Greg KH
2008-12-17 19:28 ` [PATCH 1/4] driver core: fix using 'ret' variable in unregister_dynamic_debug_module Greg Kroah-Hartman
2008-12-17 19:28 ` [PATCH 2/4] xilinx_hwicap: remove improper wording in license statement Greg Kroah-Hartman
2008-12-17 23:08   ` Alan Cox
2008-12-17 23:45     ` Greg KH [this message]
2008-12-17 19:28 ` [PATCH 3/4] driver core: add newlines to debugging enabled/disabled messages Greg Kroah-Hartman
2008-12-17 19:28 ` [PATCH 4/4] STAGING: Move staging drivers back to staging-specific menu Greg Kroah-Hartman

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=20081217234525.GA16661@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=stephen.neuendorffer@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox