From: Anton Blanchard <anton@samba.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Andreas Schwab <schwab@linux-m68k.org>,
"H. Peter Anvin" <hpa@zytor.com>, Christoph Hellwig <hch@lst.de>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Hirokazu Takata <takata@linux-m32r.org>,
James Morris <jmorris@namei.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Ingo Molnar <mingo@elte.hu>, Arnd Bergmann <arnd@arndb.de>,
Jeff Dike <jdike@addtoit.com>, Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
"Luck, Tony" <tony.luck@intel.com>,
Ralf Baechle <ralf@linux-mips.org>,
Kyle McMartin <kyle@mcmartin.ca>,
Paul Mundt <lethal@linux-sh.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: ppc64 sys_ipc breakage in 2.6.34-rc2
Date: Tue, 23 Mar 2010 09:01:38 +1100 [thread overview]
Message-ID: <20100322220138.GF24064@kryten> (raw)
In-Reply-To: <alpine.LFD.2.00.1003221102050.18017@i5.linux-foundation.org>
Hi,
> > ipc/syscall.c:17: error: conflicting types for ‘sys_ipc’
> > include/linux/syscalls.h:691: note: previous declaration of ‘sys_ipc’ was here
>
> Hmm. Right you are. Why don't I see this? (I already applied the patch)
>
> Ahh. Because this only triggers with __ARCH_WANT_SYS_IPC. But why didn't
> Anton see it then?
>
> Anyway, I assume the following fixes it. Can you verify?
Sorry, I forgot to quilt add. Stupid screw up, thanks Andreas for catching
it so quickly.
Anton
next prev parent reply other threads:[~2010-03-22 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 6:47 ppc64 sys_ipc breakage in 2.6.34-rc2 Anton Blanchard
2010-03-22 18:00 ` Andreas Schwab
2010-03-22 18:07 ` Linus Torvalds
2010-03-22 19:56 ` Andreas Schwab
2010-03-22 22:01 ` Anton Blanchard [this message]
2010-03-22 20:01 ` Christoph Hellwig
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=20100322220138.GF24064@kryten \
--to=anton@samba.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=jesper.nilsson@axis.com \
--cc=jmorris@namei.org \
--cc=kyle@mcmartin.ca \
--cc=lethal@linux-sh.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=ralf@linux-mips.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=schwab@linux-m68k.org \
--cc=schwidefsky@de.ibm.com \
--cc=takata@linux-m32r.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).