All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: John Crispin <john@phrozen.org>,
	Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MIPS: ralink: Fix missing `get_c0_perfcount_int` prototype
Date: Thu, 29 Aug 2024 10:37:45 +0200	[thread overview]
Message-ID: <ZtAzWeLojUP9cKJC@alpha.franken.de> (raw)
In-Reply-To: <20240812131803.16475-3-vincent.legoll@gmail.com>

On Mon, Aug 12, 2024 at 03:17:43PM +0200, Vincent Legoll wrote:
> Fix the following warning:
> 
>   CC      arch/mips/ralink/irq-gic.o
> arch/mips/ralink/irq-gic.c:15:5: warning: no previous prototype for 'get_c0_perfcount_int' [-Wmissing-prototypes]
>    15 | int get_c0_perfcount_int(void)
>       |     ^~~~~~~~~~~~~~~~~~~~
> 
> Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
> ---
>  arch/mips/ralink/irq-gic.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/mips/ralink/irq-gic.c b/arch/mips/ralink/irq-gic.c
> index 3bab51a5fb4c..8bc566ea00e5 100644
> --- a/arch/mips/ralink/irq-gic.c
> +++ b/arch/mips/ralink/irq-gic.c
> @@ -10,6 +10,7 @@
>  #include <linux/of.h>
>  #include <linux/irqchip.h>
>  #include <asm/mips-cps.h>
> +#include <asm/time.h>
>  
>  int get_c0_perfcount_int(void)
>  {
> -- 
> 2.46.0

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2024-08-29  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 13:17 [PATCH 0/2] MIPS: ralink: Fix missing prototypes warnings Vincent Legoll
2024-08-12 13:17 ` [PATCH 1/2] MIPS: ralink: Fix missing `plat_time_init` prototype Vincent Legoll
2024-08-29  8:37   ` Thomas Bogendoerfer
2024-08-12 13:17 ` [PATCH 2/2] MIPS: ralink: Fix missing `get_c0_perfcount_int` prototype Vincent Legoll
2024-08-29  8:37   ` Thomas Bogendoerfer [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=ZtAzWeLojUP9cKJC@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=vincent.legoll@gmail.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 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.