From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Ken Chen <kenchen@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: sched tree build warning
Date: Mon, 22 Dec 2008 11:53:57 +0100 [thread overview]
Message-ID: <20081222105357.GA21776@elte.hu> (raw)
In-Reply-To: <18767.24943.183634.866661@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> > I cannot see how the binary representation could ever change from
> > this. (and that is all that an ABI is about - it is an application
> > Binary interface. I.e. there's no ABI breakage.)
>
> Yes, the bits are the same, but that doesn't mean the types are the
> same. And we do export type definitions.
>
> I once wanted to change the ppc32 size_t definition from unsigned int to
> unsigned long to match up with ppc64. That caused more pain than it was
> worth because of exactly this issue (and also because gcc has fixed
> ideas about size_t) so I abandoned it. That's why I'm cautious about
> changing user-visible types. I'm not saying we can't do it, I'm saying
> we shouldn't do it unilaterally.
okay, so what's the timeline to double check those details and to get this
fix upstream?
Ingo
next prev parent reply other threads:[~2008-12-22 10:54 UTC|newest]
Thread overview: 38+ 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
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 [this message]
2008-12-22 12:03 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2009-04-21 0:27 Stephen Rothwell
2009-04-21 3:10 ` Gautham R Shenoy
2009-04-21 3:28 ` Stephen Rothwell
2009-04-21 6:09 ` Ingo Molnar
2009-04-21 6:21 ` Rusty Russell
2009-05-07 1:21 Stephen Rothwell
2009-05-07 6:45 ` David Rientjes
2009-05-07 7:39 ` Ingo Molnar
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=20081222105357.GA21776@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=kenchen@google.com \
--cc=linux-next@vger.kernel.org \
--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).