public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard@openedhand.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Adrian Bunk <bunk@stusta.de>, LKML <linux-kernel@vger.kernel.org>,
	torvalds@linux-foundation.org,
	David Woodhouse <dwmw2@infradead.org>,
	"Markus F.X.J. Oberhumer" <markus@oberhumer.com>
Subject: Re: [PATCH] Add LZO1X compression support to the kernel
Date: Sat, 12 May 2007 21:56:45 +0100	[thread overview]
Message-ID: <1179003405.5831.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20070512094710.43ab1b2f.akpm@linux-foundation.org>

On Sat, 2007-05-12 at 09:47 -0700, Andrew Morton wrote:
> On Sat, 12 May 2007 16:17:35 +0100 Richard Purdie <richard@openedhand.com> wrote:
> 
> > On Sat, 2007-05-12 at 13:17 +0200, Adrian Bunk wrote:
> > > On Wed, May 02, 2007 at 09:56:23AM +0100, Richard Purdie wrote:
> > > >...
> > > > I've asked the LZO author about the comments on lzo_copyright function
> > > > but the code is GPLv2 licensed so is suitable for inclusion in the
> > > > kernel.
> > > 
> > > This sounds as if LZO is GPL incompatible similar to code under
> > > the 4 clause BSD licence.
> > > 
> > > >...
> > > > +/* If you use the LZO library in a product, you *must* keep this
> > > > + * copyright string in the executable of your product.
> > > > + */
> > 
> > I've had a reply from the copyright holder/author saying he's going to
> > change this wording in the next LZO release and that the code *is* GPLv2
> > licensed as per the headers on the files.
> > 
> 
> It would be ideal if the author of that code could send us a
> signed-off-by: as per secton 11 of Documentation/SubmittingPatches.  

Section 11b says I can submit it but I've asked the author about a
signed off by line (he's cc'd) for the alleviation of any doubt.

Cheers,

Richard



  reply	other threads:[~2007-05-12 20:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  8:56 [PATCH] Add LZO1X compression support to the kernel Richard Purdie
2007-05-02  9:35 ` Pekka Enberg
2007-05-04 18:28   ` Satyam Sharma
2007-05-10  6:21 ` Andrew Morton
2007-05-10  8:26   ` David Woodhouse
2007-05-10  8:53     ` Richard Purdie
2007-05-10 14:30   ` Jan Engelhardt
2007-05-12 11:17 ` Adrian Bunk
2007-05-12 15:17   ` Richard Purdie
2007-05-12 16:47     ` Andrew Morton
2007-05-12 20:56       ` Richard Purdie [this message]
2007-05-13 11:59         ` Markus F.X.J. Oberhumer
  -- strict thread matches above, loose matches on Subject: below --
2007-05-10  8:49 Tomasz Chmielewski
2007-05-11 20:48 devzero
2007-05-13 13:06 ` Jindrich Makovicka
2007-05-12 10:41 devzero
2007-05-12 11:41 ` Jindrich Makovicka
2007-05-12 19:51   ` Satyam Sharma
2007-05-15 16:54 ` Pavel Machek

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=1179003405.5831.18.camel@localhost.localdomain \
    --to=richard@openedhand.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@oberhumer.com \
    --cc=torvalds@linux-foundation.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