From: Robert Hancock <hancockrwd@gmail.com>
To: Raz <raziebe@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>
Subject: Re: Permission to use list.h and atomic.h in user space
Date: Mon, 22 Jun 2009 18:04:41 -0600 [thread overview]
Message-ID: <4A401C19.8090102@gmail.com> (raw)
In-Reply-To: <5d96567b0906220644p4c412163m26d7cb16e6e5c58d@mail.gmail.com>
On 06/22/2009 07:44 AM, Raz wrote:
> Hello
> May I have permission to use atomic64.h ,atomic32.h and list.h in a
> proprietary software ?
> I do not know who the authors are.
> Thank you
> Raz
You would likely have to basically track down everyone who has ever
contributed to those files and get their permission, which seems
unlikely. So the short answer is almost certainly no.
With newer gcc there are atomic built-in functions which will likely do
what you want for the atomic ops at least..
prev parent reply other threads:[~2009-06-23 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d96567b0906220510q32d0280diec9a2179ed37216e@mail.gmail.com>
[not found] ` <20090622153701.1012ca3c@t61.ukuu.org.uk>
2009-06-22 13:44 ` Permission to use list.h and atomic.h in user space Raz
2009-06-22 14:10 ` Arjan van de Ven
2009-06-23 0:04 ` Robert Hancock [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=4A401C19.8090102@gmail.com \
--to=hancockrwd@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raziebe@gmail.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