From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
kenchen@google.com, paulus@samba.org, tglx@linutronix.de,
linux-next@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [patch] powerpc: change u64/s64 to a long long integer type
Date: Tue, 23 Dec 2008 00:13:46 +0100 [thread overview]
Message-ID: <20081222231346.GA4258@uranus.ravnborg.org> (raw)
In-Reply-To: <49501CC9.5040507@zytor.com>
On Mon, Dec 22, 2008 at 03:03:37PM -0800, H. Peter Anvin wrote:
> Sam Ravnborg wrote:
> > On Mon, Dec 22, 2008 at 02:43:19PM -0800, Andrew Morton wrote:
> >> On Mon, 22 Dec 2008 09:03:41 +0100
> >> Ingo Molnar <mingo@elte.hu> wrote:
> >>
> >>> Subject: powerpc: change u64/s64 to a long long integer type
> >> <applause>
> >>
> >> There are lots of other architctures that need doing though.
> >
> > I have missed the introduction.
> > Can you explain why?
> >
> > I have done a bit of sparc hacking lately and was wondering if
> > sparc needs something similar.
> >
> > cd arch/sparc
> > git grep u64 | grep -v __u64 | wc -l
> > 448
> >
>
> This should only affect 64-bit architectures.
In the sparc-next tree:
ls arch/sparc64
ls: arch/sparc64: No such file or directory
We have unified sparc and sparc64 so they are in the same arch directory now.
This will hit mainline in the upcoming merge window.
This has happended over at the sparclinux mailing list as this was
sparc/sparc64 specific stuff so no wonder you have not heard about it.
Sam
next prev parent reply other threads:[~2008-12-22 23:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 4:22 linux-next: sched tree build warning Stephen Rothwell
2008-12-22 6:47 ` Ingo Molnar
2008-12-22 6:49 ` Ken Chen
2008-12-22 7:04 ` Ingo Molnar
2008-12-22 7:19 ` Stephen Rothwell
2008-12-22 8:03 ` [patch] powerpc: change u64/s64 to a long long integer type Ingo Molnar
2008-12-22 22:43 ` Andrew Morton
2008-12-22 23:00 ` Sam Ravnborg
2008-12-22 23:03 ` H. Peter Anvin
2008-12-22 23:13 ` Sam Ravnborg [this message]
2008-12-22 23:13 ` Andrew Morton
2008-12-23 13:17 ` [PATCH] sparc64: use unsigned long long for u64 Sam Ravnborg
2008-12-23 14:42 ` [PATCH] sparc64: fix unsigned long long warnings in drivers Sam Ravnborg
2008-12-23 17:05 ` [PATCH] sparc64: use unsigned long long for u64 Ken Chen
2008-12-23 17:26 ` Sam Ravnborg
2008-12-23 17:29 ` Ken Chen
2008-12-23 17:34 ` Sam Ravnborg
2008-12-27 8:54 ` David Miller
2008-12-27 9:24 ` Sam Ravnborg
2008-12-27 9:37 ` David Miller
2008-12-27 9:49 ` Sam Ravnborg
2008-12-28 4:25 ` David Miller
2008-12-28 12:32 ` Sam Ravnborg
2008-12-31 4:40 ` [patch] powerpc: change u64/s64 to a long long integer type Stephen Rothwell
2008-12-31 7:52 ` Ingo Molnar
2008-12-22 8:14 ` linux-next: sched tree build warning Paul Mackerras
2008-12-22 8:18 ` Ingo Molnar
2008-12-22 9:44 ` Paul Mackerras
2008-12-22 10:53 ` Ingo Molnar
2008-12-22 12:03 ` Paul Mackerras
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=20081222231346.GA4258@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).