public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Christian Fredrik Kalager Schaller <Uraeus@linuxrising.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Permission to use atomic code under LGPL
Date: Fri, 31 Jan 2003 12:34:46 +0000	[thread overview]
Message-ID: <20030131123446.C19646@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1044014183.1127.13.camel@thebox>; from Uraeus@linuxrising.org on Fri, Jan 31, 2003 at 12:56:24PM +0100

On Fri, Jan 31, 2003 at 12:56:24PM +0100, Christian Fredrik Kalager Schaller wrote:
> I got no objections to my request to use these few lines under the LGPL
> so I will now update our sourcefile to make sure linus gets copyright
> and origin is informed of. Thanks a lot guys!

In any case, "no objections" and certainly "no response" is not the same
as "being granted permission".  You can not take silence as a positive
outcome to these questions, unless you're on a deathwish to get sued.

You need *explicit* permission of the author in order to use any code
in a way not covered by the license under which that code is distributed.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      parent reply	other threads:[~2003-01-31 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 17:52 Permission to use atomic code under LGPL Christian Fredrik Kalager Schaller
2003-01-30  7:46 ` Pavel Machek
2003-01-31 11:56 ` Christian Fredrik Kalager Schaller
2003-01-31 12:01   ` Christoph Hellwig
2003-01-31 12:12     ` Christian Fredrik Kalager Schaller
2003-01-31 12:47       ` Mike A. Harris
2003-01-31 12:34   ` Russell King [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=20030131123446.C19646@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Uraeus@linuxrising.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