From: David Woodhouse <dwmw2@infradead.org>
To: Albert Cahalan <acahalan@gmail.com>
Cc: arjan@infradead.org, maillist@jg555.com, ralf@linux-mips.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: 2.6.18 Headers - Long
Date: Sat, 15 Jul 2006 22:47:00 +0100 [thread overview]
Message-ID: <1153000020.8427.16.camel@pmac.infradead.org> (raw)
In-Reply-To: <787b0d920607151409q4d0dfcc1wc787d9dfe7b0a897@mail.gmail.com>
On Sat, 2006-07-15 at 17:09 -0400, Albert Cahalan wrote:
> David Woodhouse writes:
> > Kernel headers are _not_ a library of random crap for userspace to
> > use.
> Don't blame app developers if they go for what is good.
> To stop them, provide the goodness in a sane way.
> (alternately, make the Linux code suck ass more than POSIX)
Kernel headers are _not_ a library of random crap for userspace to use.
There is no justification for asm/atomic.h being installed
in /usr/include. Especially since, as Arjan points out, it doesn't
actually provide atomic operations in many cases anyway.
However, the kernel is released under a licence which allows you to
re-use code from it if you really want. If you want to provide a
'libkernelstuff', the GPL permits you to do that. The kernel's ABI
headers (and lkml) are not the appropriate place for such a project
though. If you want to do that, take it where the C++ and microkernel
people go.
Btw, your mail client omitted the References: and In-Reply-To: headers
which RFC2822 says it SHOULD have included. On a list with as much
traffic as linux-kernel, that's _very_ suboptimal, because you've
detached your message from the thread to which you replied. Please try
to fix or work around that.
--
dwmw2
next prev parent reply other threads:[~2006-07-15 21:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 21:09 Albert Cahalan
2006-07-15 21:19 ` Arjan van de Ven
2006-07-17 5:21 ` Ralf Baechle
2006-07-15 21:44 ` Adrian Bunk
2006-07-15 21:47 ` David Woodhouse [this message]
2006-07-16 6:18 ` Albert Cahalan
2006-07-16 6:26 ` Arjan van de Ven
2006-07-16 8:05 ` David Woodhouse
2006-07-16 8:20 ` Jakub Jelinek
2006-07-16 12:34 ` Kyle Moffett
2006-07-16 12:48 ` Russell King
2006-07-16 18:38 ` Albert Cahalan
2006-07-16 18:53 ` Russell King
2006-07-16 19:22 ` Albert Cahalan
2006-07-16 19:41 ` Russell King
2006-07-17 1:26 ` Arjan van de Ven
2006-07-17 1:23 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 0:35 Jim Gifford
2006-07-14 0:25 ` David Woodhouse
2006-07-14 2:18 ` Jim Gifford
2006-07-14 18:55 ` David Woodhouse
2006-07-14 19:28 ` Jim Gifford
2006-07-14 19:39 ` Arjan van de Ven
2006-07-14 20:16 ` David Woodhouse
2006-07-14 20:19 ` David Miller
2006-07-14 20:57 ` Jim Gifford
2006-07-15 4:33 ` Randy.Dunlap
2006-07-16 14:08 ` Nix
2006-07-15 7:19 ` David Woodhouse
2006-07-15 7:08 ` David Woodhouse
2006-07-14 19:57 ` David Woodhouse
2006-07-14 20:06 ` Erik Andersen
2006-07-14 20:19 ` Christoph Hellwig
2006-08-26 16:09 ` David Woodhouse
2006-08-29 12:25 ` Ralf Baechle
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=1153000020.8427.16.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=acahalan@gmail.com \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®