mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-mips@vger.kernel.org, jonas.gorski@gmail.com,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] MIPS: BCM63XX: Fix missing prototypes
Date: Fri, 26 Jan 2024 11:13:23 +0100	[thread overview]
Message-ID: <ZbOFw7m7CX8SHy4F@alpha.franken.de> (raw)
In-Reply-To: <20240123174701.210922-1-f.fainelli@gmail.com>

On Tue, Jan 23, 2024 at 09:46:54AM -0800, Florian Fainelli wrote:
> Most of the symbols for which we do not have a prototype can actually be
> made static and for the few that cannot, there is already a declaration
> in a header for it.
> 
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  arch/mips/bcm63xx/boards/board_bcm963xx.c | 2 +-
>  arch/mips/bcm63xx/dev-rng.c               | 2 +-
>  arch/mips/bcm63xx/dev-uart.c              | 1 +
>  arch/mips/bcm63xx/dev-wdt.c               | 2 +-
>  arch/mips/bcm63xx/irq.c                   | 2 +-
>  arch/mips/bcm63xx/setup.c                 | 2 +-
>  arch/mips/bcm63xx/timer.c                 | 2 +-
>  7 files changed, 7 insertions(+), 6 deletions(-)

applied to mips-fixes.

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-01-26 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 17:46 Florian Fainelli
2024-01-26 10:13 ` 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=ZbOFw7m7CX8SHy4F@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=f.fainelli@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.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®