All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org
Subject: Re: [PATCH 1/1] x86/io_apic: suppress compiler warning
Date: Fri, 9 Oct 2015 10:38:00 +0800	[thread overview]
Message-ID: <56172888.90005@linux.intel.com> (raw)
In-Reply-To: <1444319718-33529-1-git-send-email-andriy.shevchenko@linux.intel.com>

On 2015/10/8 23:55, Andy Shevchenko wrote:
> We have to define internally used function as static, otherwise the following
> warning will be generated:
> 
> arch/x86/kernel/apic/io_apic.c:532:6: warning: no previous prototype for ‘eoi_ioapic_pin’ [-Wmissing-prototypes]
Hi Andy,
	Thanks for fixing this.
Reviewed-by: Jiang Liu <jiang.liu@linux.intel.com>

> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  arch/x86/kernel/apic/io_apic.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> index 5c60bb1..b5a0e3c 100644
> --- a/arch/x86/kernel/apic/io_apic.c
> +++ b/arch/x86/kernel/apic/io_apic.c
> @@ -529,7 +529,7 @@ static void __eoi_ioapic_pin(int apic, int pin, int vector)
>  	}
>  }
>  
> -void eoi_ioapic_pin(int vector, struct mp_chip_data *data)
> +static void eoi_ioapic_pin(int vector, struct mp_chip_data *data)
>  {
>  	unsigned long flags;
>  	struct irq_pin_list *entry;
> 

      reply	other threads:[~2015-10-09  2:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 15:55 [PATCH 1/1] x86/io_apic: suppress compiler warning Andy Shevchenko
2015-10-09  2:38 ` Jiang Liu [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=56172888.90005@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.