All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: TJ <linux@tjworld.net>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Casual J. Programmer" <casualprogrammer@googlemail.com>
Subject: Re: Agere Hermes source-code: copyright situation
Date: Wed, 1 Oct 2008 13:00:39 -0700	[thread overview]
Message-ID: <20081001200039.GA29874@kroah.com> (raw)
In-Reply-To: <1222879229.17264.4.camel@hephaestion>

On Wed, Oct 01, 2008 at 05:40:29PM +0100, TJ wrote:
> On Wed, 2008-10-01 at 14:13 +0400, Andrey Borzenkov wrote:
> > And it is not GPL'ed, of course. I attach E-Mail I received a while
> > back with answere from Agere legal department.
> 
> I'm attaching the original email I sent to Agere and their response for
> the record, hoping it helps clarify the legal position.

Very nice, thanks for forwarding this on.

As the license is BSD, that means we can place it in the kernel tree.
Do you all mind if I add it to the drivers/staging/ directory so you can
work on cleaning it up within the main kernel tree infrastructure?

thanks,

greg k-h

  parent reply	other threads:[~2008-10-01 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  5:49 Building two (external) modules from the same sources Andrey Borzenkov
2008-10-01  3:19 ` Greg KH
2008-10-01 10:13   ` Andrey Borzenkov
2008-10-01 10:13     ` Andrey Borzenkov
     [not found]     ` <1222879229.17264.4.camel@hephaestion>
2008-10-01 20:00       ` Greg KH [this message]
2008-10-01 23:00         ` Agere Hermes source-code: copyright situation Dave
2008-10-02  2:37           ` Andrey Borzenkov
2008-10-02 17:44             ` Dave
2008-10-02 20:00             ` Greg KH
2008-10-02 20:31               ` Dan Williams
2008-10-02 20:37                 ` Greg KH
2008-10-02 21:28                   ` Dan Williams
2008-10-01 20:05     ` Building two (external) modules from the same sources Greg KH
2008-10-01 22:27       ` TJ

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=20081001200039.GA29874@kroah.com \
    --to=greg@kroah.com \
    --cc=arvidjaar@mail.ru \
    --cc=casualprogrammer@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@tjworld.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.