mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Tautschnig, Michael" <tautschn@amazon.co.uk>
Cc: kbuild-all@01.org, "x86@kernel.org" <x86@kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Jaswinder Singh <jaswinder@infradead.org>,
	Andi Kleen <ak@linux.intel.com>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] x86/sigreturn: use SYSCALL_DEFINE0
Date: Tue, 20 Mar 2018 04:17:37 +0800	[thread overview]
Message-ID: <201803200440.2jyQrGjo%fengguang.wu@intel.com> (raw)
In-Reply-To: <9C9981F4-0E5E-42A7-8788-70F3DEAD258D@amazon.com>

[-- Attachment #1: Type: text/plain, Size: 2576 bytes --]

Hi Michael,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v4.16-rc4]
[also build test ERROR on next-20180319]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Tautschnig-Michael/x86-sigreturn-use-SYSCALL_DEFINE0/20180316-110516
config: i386-randconfig-c0-03200324 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (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)
    ^~~~~~~~~~~~~~~
   In file included from arch/x86/kernel/signal.c:45:0:
   arch/x86/include/asm/syscalls.h:37:26: note: previous declaration of 'sys_sigreturn' was here
    asmlinkage unsigned long sys_sigreturn(void);
                             ^~~~~~~~~~~~~
--
   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)
    ^~~~~~~~~~~~~~~
   In file included from arch/x86//kernel/signal.c:45:0:
   arch/x86/include/asm/syscalls.h:37:26: note: previous declaration of 'sys_sigreturn' was here
    asmlinkage unsigned long sys_sigreturn(void);
                             ^~~~~~~~~~~~~

vim +/sys_sigreturn +194 include/linux/syscalls.h

bed1ffca Frederic Weisbecker 2009-03-13  191  
bed1ffca Frederic Weisbecker 2009-03-13  192  #define SYSCALL_DEFINE0(sname)					\
99e621f7 Al Viro             2013-03-05  193  	SYSCALL_METADATA(_##sname, 0);				\
bed1ffca Frederic Weisbecker 2009-03-13 @194  	asmlinkage long sys_##sname(void)
bed1ffca Frederic Weisbecker 2009-03-13  195  

:::::: The code at line 194 was first introduced by commit
:::::: bed1ffca022cc876fb83161d26670e9b5d3cf36b tracing/syscalls: core infrastructure for syscalls tracing, enhancements

:::::: TO: Frederic Weisbecker <fweisbec@gmail.com>
:::::: CC: Ingo Molnar <mingo@elte.hu>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28743 bytes --]

  parent reply	other threads:[~2018-03-19 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  9:41 Tautschnig, Michael
2018-03-14 20:04 ` Thomas Gleixner
2018-03-14 20:36   ` Dominik Brodowski
2018-03-14 20:45 ` [tip:x86/urgent] x86/sigreturn: Use SYSCALL_DEFINE0 tip-bot for Tautschnig, Michael
2018-03-19 20:17 ` kbuild test robot [this message]
2018-03-19 22:27 ` [PATCH] x86/sigreturn: use SYSCALL_DEFINE0 kbuild test robot

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=201803200440.2jyQrGjo%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jaswinder@infradead.org \
    --cc=kbuild-all@01.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=mingo@redhat.com \
    --cc=tautschn@amazon.co.uk \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®