From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: WangYuli <wangyuli@uniontech.com>
Cc: chenlinxuan@uniontech.com, guanwentao@uniontech.com,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
macro@orcam.me.uk, niecheng1@uniontech.com,
zhanjun@uniontech.com
Subject: Re: [PATCH 1/7] MIPS: dec: Declare which_prom() as static
Date: Thu, 27 Feb 2025 11:00:18 +0100 [thread overview]
Message-ID: <Z8A3sucKlB5i0zd9@alpha.franken.de> (raw)
In-Reply-To: <22CF8506E42636AF+20250218125431.665670-1-wangyuli@uniontech.com>
On Tue, Feb 18, 2025 at 08:54:31PM +0800, WangYuli wrote:
> Declare which_prom() as static to suppress gcc compiler warning that
> 'missing-prototypes'. This function is not intended to be called
> from other parts.
>
> Fix follow error with gcc-14 when -Werror:
>
> arch/mips/dec/prom/init.c:45:13: error: no previous prototype for ‘which_prom’ [-Werror=missing-prototypes]
> 45 | void __init which_prom(s32 magic, s32 *prom_vec)
> | ^~~~~~~~~~
> cc1: all warnings being treated as errors
> make[6]: *** [scripts/Makefile.build:207: arch/mips/dec/prom/init.o] Error 1
> make[5]: *** [scripts/Makefile.build:465: arch/mips/dec/prom] Error 2
> make[5]: *** Waiting for unfinished jobs....
>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
> ---
> arch/mips/dec/prom/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/dec/prom/init.c b/arch/mips/dec/prom/init.c
> index cb12eb211a49..8d74d7d6c05b 100644
> --- a/arch/mips/dec/prom/init.c
> +++ b/arch/mips/dec/prom/init.c
> @@ -42,7 +42,7 @@ int (*__pmax_close)(int);
> * Detect which PROM the DECSTATION has, and set the callback vectors
> * appropriately.
> */
> -void __init which_prom(s32 magic, s32 *prom_vec)
> +static void __init which_prom(s32 magic, s32 *prom_vec)
> {
> /*
> * No sign of the REX PROM's magic number means we assume a non-REX
> --
> 2.47.2
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 ]
next prev parent reply other threads:[~2025-02-27 10:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 12:51 [PATCH 0/7] MIPS: decstation_64_defconfig: Compile the kernel with warnings as errors WangYuli
2025-02-18 12:54 ` [PATCH 1/7] MIPS: dec: Declare which_prom() as static WangYuli
2025-02-27 10:00 ` Thomas Bogendoerfer [this message]
2025-02-18 12:56 ` [PATCH 2/7] MIPS: dec: Create reset.h WangYuli
2025-02-27 9:45 ` Thomas Bogendoerfer
2025-02-27 10:14 ` WangYuli
2025-02-18 12:57 ` [PATCH 3/7] MIPS: cevt-ds1287: Add missing ds1287.h include WangYuli
2025-02-27 10:00 ` Thomas Bogendoerfer
2025-02-18 12:57 ` [PATCH 4/7] MIPS: ds1287: Match ds1287_set_base_clock() function types WangYuli
2025-02-27 10:00 ` Thomas Bogendoerfer
2025-02-18 12:58 ` [PATCH 5/7] MIPS: dec: Remove dec_irq_dispatch() WangYuli
2025-02-27 10:01 ` Thomas Bogendoerfer
2025-02-28 16:01 ` Maciej W. Rozycki
2025-03-03 4:23 ` WangYuli
2025-03-03 9:06 ` Thomas Bogendoerfer
2025-02-18 13:00 ` [PATCH 6/7] MIPS: decstation_64_defconfig: Update configs dependencies WangYuli
2025-02-18 13:00 ` [PATCH 7/7] MIPS: decstation_64_defconfig: Compile the kernel with warnings as errors WangYuli
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=Z8A3sucKlB5i0zd9@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenlinxuan@uniontech.com \
--cc=guanwentao@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=niecheng1@uniontech.com \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox