All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Georg Klug" <gklug@giga-stream.de>
Cc: "Tom Rini" <trini@kernel.crashing.org>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: AW: Possible problem in asm/bitops.h
Date: Tue, 17 Dec 2002 21:16:03 +1100	[thread overview]
Message-ID: <15870.63843.171445.243166@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <FFECLICFNBJAHONLGAKMAEFOCHAA.gklug@giga-stream.de>


Georg Klug writes:

> Oops, I thought, that the directories /usr/include/linux as well as
> /usr/include/asm should come directly from the kernel (either as a copy

That is how it used to be done, but that way of doing things has been
deprecated for a long time now.  /usr/include/{linux,asm} are part of
glibc these days.

> or symbolically linked). In that case those include files should always
> be prepared to be included in a userland application. Am I right with this?
>
> I also thought, that the asm-ppc/bitops.h should provide the same
> functionality as its pendant in asm-i386/ which lets userland applications
> use some static inline functions like set_bit() clear_bit() and change_bit().
> I actually don't know whether those functions are needed outside the kernel,
> so I cannot tell whether it is correct or not. But IMO it should be done
> the same way on all plattforms. Would you agree?

The policy is the same on all architectures: userland programs should
not include kernel headers.  The architectures differ in the extent to
which this is enforced, that's all.

Paul.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-12-17 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 15:31 Possible problem in asm/bitops.h Georg Klug
2002-12-12 15:28 ` Tom Rini
2002-12-17  9:10   ` AW: " Georg Klug
2002-12-17 10:16     ` Paul Mackerras [this message]
2002-12-17 14:59     ` Tom Rini

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=15870.63843.171445.243166@argo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=gklug@giga-stream.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 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.