linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:master 22/22] arch/x86//kernel/cpu/mcheck/therm_throt.c:394:39: error: conflicting types for 'smp_thermal_interrupt'
Date: Wed, 14 Nov 2018 16:12:29 +0100	[thread overview]
Message-ID: <20181114151229.GA13183@zn.tnic> (raw)
In-Reply-To: <201811142348.uUmuZUqI%fengguang.wu@intel.com>

On Wed, Nov 14, 2018 at 11:00:52PM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> head:   449637df6faa8cd9a7f9cdf25589445f0dab2371
> commit: 449637df6faa8cd9a7f9cdf25589445f0dab2371 [22/22] Merge branch 'x86/cleanups'
> config: x86_64-lkp (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
>         git checkout 449637df6faa8cd9a7f9cdf25589445f0dab2371
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> All errors (new ones prefixed by >>):
> 
> >> arch/x86//kernel/cpu/mcheck/therm_throt.c:394:39: error: conflicting types for 'smp_thermal_interrupt'
>     asmlinkage __visible void __irq_entry smp_thermal_interrupt(void)
>                                           ^~~~~~~~~~~~~~~~~~~~~
>    In file included from arch/x86//kernel/cpu/mcheck/therm_throt.c:28:0:
>    arch/x86/include/asm/traps.h:107:17: note: previous declaration of 'smp_thermal_interrupt' was here
>     asmlinkage void smp_thermal_interrupt(struct pt_regs *regs);
>                     ^~~~~~~~~~~~~~~~~~~~~
> 
> vim +/smp_thermal_interrupt +394 arch/x86//kernel/cpu/mcheck/therm_throt.c
> 
> a65c88dd Hidetoshi Seto  2009-06-15  393  
> d813dfb2 Borislav Petkov 2018-11-09 @394  asmlinkage __visible void __irq_entry smp_thermal_interrupt(void)
> cf910e83 Seiji Aguchi    2013-06-20  395  {
> cf910e83 Seiji Aguchi    2013-06-20  396  	entering_irq();
> cf910e83 Seiji Aguchi    2013-06-20  397  	trace_thermal_apic_entry(THERMAL_APIC_VECTOR);
> 0f42ae28 Thomas Gleixner 2017-08-28  398  	inc_irq_stat(irq_thermal_count);
> 0f42ae28 Thomas Gleixner 2017-08-28  399  	smp_thermal_vector();
> cf910e83 Seiji Aguchi    2013-06-20  400  	trace_thermal_apic_exit(THERMAL_APIC_VECTOR);
> cf910e83 Seiji Aguchi    2013-06-20  401  	exiting_ack_irq();
> cf910e83 Seiji Aguchi    2013-06-20  402  }
> cf910e83 Seiji Aguchi    2013-06-20  403  
> 
> :::::: The code at line 394 was first introduced by commit
> :::::: d813dfb28641306f66cf1e2c3586f39ab4f84b27 x86/mce: Fix -Wmissing-prototypes warnings

Already fixed:

https://git.kernel.org/tip/68b5e4326e4b8ac9080835005d8254fed0fb3c56

Thx.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

      reply	other threads:[~2018-11-14 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 15:00 [tip:master 22/22] arch/x86//kernel/cpu/mcheck/therm_throt.c:394:39: error: conflicting types for 'smp_thermal_interrupt' kbuild test robot
2018-11-14 15:12 ` Borislav Petkov [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=20181114151229.GA13183@zn.tnic \
    --to=bp@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).