From: Mike Frysinger <vapier@gentoo.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] linux/types.h: always export 64bit aligned defines
Date: Tue, 29 Jan 2008 19:16:20 -0500 [thread overview]
Message-ID: <200801291916.21133.vapier@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801292030190.14907@fbirervta.pbzchgretzou.qr>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On Tuesday 29 January 2008, Jan Engelhardt wrote:
> On Jan 27 2008 21:33, Andrew Morton wrote:
> >On Sat, 26 Jan 2008 04:23:21 -0500 Mike Frysinger <vapier@gentoo.org>
wrote:
> >> Some kernel headers exported to userspace rely on these 64bit
> >> aligned defines. However, they are hidden behind
> >> __KERNEL_STRICT_NAMES at the moment which means most of the time,
> >> they're never actually available.
>
> Wrong way.
i'm thinking the right way, i just may not have expressed it completely
clearly ...
> They are inside #ifndef __KERNEL_STRICT_NAMES, so
> they _are_ available to userspace.
for all practical purposes, they are not. glibc will define
__KERNEL_STRICT_NAMES because (like a sane C lib), it defines all of the
basic types that the kernel also defines.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-01-30 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 9:23 Mike Frysinger
2008-01-28 5:33 ` Andrew Morton
2008-01-29 19:43 ` Jan Engelhardt
2008-01-30 0:16 ` Mike Frysinger [this message]
2008-01-30 0:37 ` Jan Engelhardt
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=200801291916.21133.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome