From: Thomas Gleixner <tglx@linutronix.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "Tautschnig, Michael" <tautschn@amazon.co.uk>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Michael Tautschnig <tautschn@amazon.com>
Subject: Re: [tip:x86/urgent 2/2] include/linux/syscalls.h:194:18: error: conflicting types for 'sys_sigreturn'
Date: Wed, 14 Mar 2018 22:27:13 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1803142226120.1946@nanos.tec.linutronix.de> (raw)
In-Reply-To: <201803150455.fCJ6BtVM%fengguang.wu@intel.com>
On Thu, 15 Mar 2018, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
> head: 1227b344de283f96c41de02cde4b26d5290f5302
> commit: 1227b344de283f96c41de02cde4b26d5290f5302 [2/2] x86/sigreturn: Use SYSCALL_DEFINE0
> config: i386-randconfig-x073-201810 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> git checkout 1227b344de283f96c41de02cde4b26d5290f5302
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from arch/x86/kernel/signal.c:28:0:
> >> include/linux/syscalls.h:194:18: error: conflicting types for 'sys_sigreturn'
> asmlinkage long sys_##sname(void)
> ^
> >> arch/x86/kernel/signal.c:605:1: note: in expansion of macro 'SYSCALL_DEFINE0'
> SYSCALL_DEFINE0(sigreturn)
> ^~~~~~~~~~~~~~~
Zapped the commit. Michael, can you please have a look?
Thanks,
tglx
prev parent reply other threads:[~2018-03-14 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 20:56 kbuild test robot
2018-03-14 21:27 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1803142226120.1946@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tautschn@amazon.co.uk \
--cc=tautschn@amazon.com \
--cc=tipbuild@zytor.com \
/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
all inboxes | Powered by JetHome®