From: Clemens Ladisch <clemens@ladisch.de>
To: David Miller <davemiller2222@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: legal question regarding use of glibc headers in /usr/include/linux
Date: Fri, 16 Sep 2011 09:35:49 +0200 [thread overview]
Message-ID: <4E72FC55.1000909@ladisch.de> (raw)
In-Reply-To: <CA+o4b4fpXtF+LgLREPdjY7N06vwhCdOwRWgn-sQZYhL44=w+zA@mail.gmail.com>
David Miller wrote:
> ... some linux kernel headers in /usr/include/linux.
> My question now is: Can I include these headers (e.g. #include
> <linux/types.h>) since they seem to be normal glibc headers that seem
> to be intended to be included in user-space programs that are
> proprietary.
Read the clarification that Linus prepended to the COPYING file in the
kernel tree.
Regards,
Clemens
prev parent reply other threads:[~2011-09-16 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 19:57 legal question regarding use of glibc headers in /usr/include/linux David Miller
2011-09-16 7:35 ` Clemens Ladisch [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=4E72FC55.1000909@ladisch.de \
--to=clemens@ladisch.de \
--cc=davemiller2222@googlemail.com \
--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