From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH resend] asm/types.h: All architectures use int-ll64.h in kernelspace
Date: Sat, 13 Aug 2011 23:25:59 +0200 [thread overview]
Message-ID: <1665974.2LGtkbyJmJ@wuerfel> (raw)
In-Reply-To: <alpine.DEB.2.00.1108132152050.18053@ayla.of.borg>
On Saturday 13 August 2011 21:53:43 Geert Uytterhoeven wrote:
> Now all 64-bit architectures have been converted to int-ll64.h, we can
> deprecate int-l64.h in kernelspace:
> - Add a check to prevent new architectures from using int-l64.h in
> kernelspace,
> - Update documentation, as the casts to (unsigned) long long are no longer
> needed.
>
> For backwards compatibility, alpha, ia64, mips, and powerpc still use
> int-l64.h in userspace.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> For the documentation parts:
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
I believe that Al Viro is working on a patch to unify all umode_t definitions
so that it becomes unsigned short everywhere. Once that is done,
asm-generic/int-ll64.h can become asm-generic/types.h and all architectures
can use that.
Arnd
next prev parent reply other threads:[~2011-08-13 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 19:53 [PATCH resend] asm/types.h: All architectures use int-ll64.h in kernelspace Geert Uytterhoeven
2011-08-13 21:25 ` Arnd Bergmann [this message]
2011-08-13 21:25 ` Arnd Bergmann
2012-02-11 9:44 ` Al Viro
2012-02-11 9:44 ` Al Viro
2012-02-13 2:59 ` Arnd Bergmann
2012-02-13 2:59 ` Arnd Bergmann
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=1665974.2LGtkbyJmJ@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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