linux-kernel - Re: [PATCH 3/4] mips: zboot: Fix "no previous prototype" build warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Zdhi4ArYz+Ex/4xD@alpha.franken.de>
Date: Fri, 23 Feb 2024 10:18:24 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Serge Semin <fancer.lancer@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiri Slaby <jirislaby@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	Jiaxun Yang <jiaxun.yang@...goat.com>,
	Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
	Stephen Rothwell <sfr@...hwell.id.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-mips@...r.kernel.org, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] mips: zboot: Fix "no previous prototype" build
 warning

On Thu, Feb 15, 2024 at 08:17:28PM +0300, Serge Semin wrote:
> Without having the putc() prototype forwardly declared the next
> build-warning is printed:
> 
> arch/mips/boot/compressed/uart-prom.c:6:6: warning: no previous prototype for ‘putc’ [-Wmissing-prototypes]
> ...
> 
> Fix that by adding the "decompress.h" header file with the putc() function
> declaration to the source files which have the method redefined.
> 
> Signed-off-by: Serge Semin <fancer.lancer@...il.com>
> ---
>  arch/mips/boot/compressed/uart-16550.c   | 2 ++
>  arch/mips/boot/compressed/uart-alchemy.c | 2 ++
>  arch/mips/boot/compressed/uart-prom.c    | 2 ++
>  3 files changed, 6 insertions(+)

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 ]