From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: patches@lists.linux.dev, linux-mips@vger.kernel.org,
linux-edac@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 0/8] MIPS: Octeon: fix missing function prototype warnings
Date: Tue, 17 Nov 2026 17:09:16 +0100 [thread overview]
Message-ID: <avx8LNi5O5926c_W@alpha.franken.de> (raw)
In-Reply-To: <20261101234657.1820661-1-rdunlap@infradead.org>
On Sun, Nov 01, 2026 at 03:46:49PM -0800, Randy Dunlap wrote:
> Add missing function prototypes to header files in most cases;
> use the header files in the C source files.
> In 2 cases, make the functions static so that no prototype is
> needed.
>
> v2 changes:
> [PATCH v2 1/8] add more cache prototypes to fix mm/c-octeon build warnings
>
> series:
> [PATCH v2 1/8] MIPS: mm/c-octeon: fix missing function prototype warnings
> [PATCH v2 2/8] MIPS: Octeon: cvmx-helper: fix missing function prototype warning
> [PATCH v2 3/8] MIPS: Octeon: cvmx-interrupt: fix missing function prototype warning
> [PATCH v2 4/8] MIPS: c-octeon: fix missing function prototype warning
> [PATCH v2 5/8] MIPS: Octeon: octeon-platform: fix missing function prototype warning
> [PATCH v2 6/8] MIPS: msi-octeon: fix missing function prototype warning
> [PATCH v2 7/8] MIPS: Octeon: pci: fix missing function prototype warnings
> [PATCH v2 8/8] MIPS: Octeon: octeon.h: fix missing function prototype warning
>
>
> arch/mips/cavium-octeon/executive/cvmx-helper-errata.c | 1 +
> arch/mips/cavium-octeon/executive/cvmx-helper.c | 1 +
> arch/mips/cavium-octeon/executive/cvmx-interrupt-rsl.c | 2 --
> arch/mips/cavium-octeon/setup.c | 2 --
> arch/mips/include/asm/octeon/cvmx-gmxx-defs.h | 1 +
> arch/mips/include/asm/octeon/octeon.h | 3 +++
> arch/mips/include/asm/r4kcache.h | 5 +++++
> arch/mips/mm/c-octeon.c | 1 -
> arch/mips/pci/msi-octeon.c | 2 +-
> arch/mips/pci/pci-octeon.c | 2 +-
> arch/mips/pci/pcie-octeon.c | 2 +-
> drivers/edac/octeon_edac-pc.c | 4 +---
> 12 files changed, 15 insertions(+), 11 deletions(-)
>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
> Cc: linux-edac@vger.kernel.org
> Cc: linux-watchdog@vger.kernel.org
series 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: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:46 [PATCH v2 0/8] MIPS: Octeon: fix missing function prototype warnings Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 1/8] MIPS: mm/c-octeon: " Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 2/8] MIPS: Octeon: cvmx-helper: fix missing function prototype warning Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 3/8] MIPS: Octeon: cvmx-interrupt: " Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 4/8] MIPS: c-octeon: " Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 5/8] MIPS: Octeon: octeon-platform: " Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 6/8] MIPS: msi-octeon: " Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 7/8] MIPS: Octeon: pci: fix missing function prototype warnings Randy Dunlap
2026-11-01 23:46 ` [PATCH v2 8/8] MIPS: Octeon: octeon.h: fix missing function prototype warning Randy Dunlap
2026-11-17 16:09 ` 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=avx8LNi5O5926c_W@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.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