From: Arnd Bergmann <arnd@arndb.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
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>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH resend] asm/types.h: All architectures use int-ll64.h in kernelspace
Date: Mon, 13 Feb 2012 02:59:32 +0000 [thread overview]
Message-ID: <201202130259.33347.arnd@arndb.de> (raw)
In-Reply-To: <20120211094444.GL23916@ZenIV.linux.org.uk>
On Saturday 11 February 2012, Al Viro wrote:
> Umm... That has happened and yes, asm-generic/types.h is currently
> equivalent to asm-generic/int-ll64.h. What exactly are you planning
> to do? Just rename the latter to the former and do search-and-replace
> over the tree? We still have places that pull int-l64.h, albeit only
> !__KERNEL__ ones (i.e. everything under #ifdef __KERNEL__ in there
> seems to be killable)...
>
> AFAICS, for quite a few of those guys we can simply add bitsperlong.h
> and add types.h to generic-y; is that the plan?
Yes, I think both would be good cleanups. Maybe David Howells can comment
as well since his user api split is going to change that a bit:
We end up needing only a separate version of uapi/asm/types.h for
alpha/ia64/mips64/powerpc64, while the in-kernel file is ok.
Arnd
next prev parent reply other threads:[~2012-02-13 2:59 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
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 [this message]
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=201202130259.33347.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--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