From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-mips@vger.kernel.org, macro@orcam.me.uk,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] MIPS: SiByte: Fix missing function prototypes
Date: Tue, 17 Nov 2026 17:16:27 +0100 [thread overview]
Message-ID: <avx927r8iDC8fRDj@alpha.franken.de> (raw)
In-Reply-To: <20261113191933.477395-1-f.fainelli@gmail.com>
On Fri, Nov 13, 2026 at 11:19:02AM -0800, Florian Fainelli wrote:
> The SB1250 SWARM build reports missing prototypes for platform time
> initialization, SoC setup, IRQ and SMP helpers, and both RTC backends.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Changes in v2:
>
> - corrected warning reported by kbuild test robot by gating the
> inclusion of sb1250.h to avoid warnings on bcm63xx_defconfig
>
> arch/mips/include/asm/sibyte/sb1250.h | 17 +++++++++++++++++
> arch/mips/mm/cerr-sb1.c | 2 --
> arch/mips/mm/tlbex.c | 11 +++++++----
> arch/mips/sibyte/bcm1480/irq.c | 4 +---
> arch/mips/sibyte/bcm1480/smp.c | 6 +-----
> arch/mips/sibyte/bcm1480/time.c | 4 ++--
> arch/mips/sibyte/common/bus_watcher.c | 2 +-
> arch/mips/sibyte/sb1250/irq.c | 4 +---
> arch/mips/sibyte/sb1250/smp.c | 6 +-----
> arch/mips/sibyte/sb1250/time.c | 4 ++--
> arch/mips/sibyte/swarm/rtc.h | 15 +++++++++++++++
> arch/mips/sibyte/swarm/rtc_m41t81.c | 1 +
> arch/mips/sibyte/swarm/rtc_xicor1241.c | 1 +
> arch/mips/sibyte/swarm/setup.c | 18 ++----------------
> 14 files changed, 52 insertions(+), 43 deletions(-)
> create mode 100644 arch/mips/sibyte/swarm/rtc.h
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 ]
prev parent reply other threads:[~2026-11-17 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 19:19 [PATCH v2] MIPS: SiByte: Fix missing function prototypes Florian Fainelli
2026-11-17 16:16 ` 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=avx927r8iDC8fRDj@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
/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