[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240215171740.14550-1-fancer.lancer@gmail.com>
Date: Thu, 15 Feb 2024 20:17:25 +0300
From: Serge Semin <fancer.lancer@...il.com>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Jiaxun Yang <jiaxun.yang@...goat.com>
Cc: Serge Semin <fancer.lancer@...il.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: [PATCH 0/4] MIPS: Fix missing proto and passing arg warnings
After getting my local tree rebased onto the kernel 6.8-rc3 the MIPS32
kernel build procedure produced a couple of warnings which I suggest to
fix in the framework of this series.
A first warning is of the "no previous prototype for `<func>`" type. In
particular my arch-specific code has the mips_cm_l2sync_phys_base() method
re-defined, but even though the function is global it' prototype isn't
declared anywhere. Fix that by adding the method prototype declaration to
the mips/include/asm/mips-cm.h header file. A similar solution was
provided for the methods:
__mips_cm_l2sync_phys_base()
mips_cm_phys_base()
__mips_cm_phys_base()
too (Please see the patches 1/4 and 2/4 notes section for an alternative
suggestion of the way to fix the warning).
One more case of the denoted warning I spotted in the self-extracting
kernel (so called zboot) with the debug printouts enabled. In particular
there are several putc() method re-definitions available in:
arch/mips/boot/compressed/uart-prom.c
arch/mips/boot/compressed/uart-16550.c
arch/mips/boot/compressed/uart-alchemy.c
All of these files lacked the prototype declaration what caused having the
"no previous prototype for ‘putc’" printed on my build with the next
configs enabled:
CONFIG_SYS_SUPPORTS_ZBOOT=y
CONFIG_SYS_SUPPORTS_ZBOOT_UART_PROM=y
CONFIG_ZBOOT_LOAD_ADDRESS=0x85100000
CONFIG_DEBUG_ZBOOT=y
The second warning is of the "passing argument <x> of ‘<func>’ from
incompatible pointer type" type which I discovered in the
drivers/tty/mips_ejtag_fdc.c driver. The problem most likely happened due
to the commit ce7cbd9a6c81 ("tty: mips_ejtag_fdc: use u8 for character
pointers").
That's it for today.) Thanks for review in advance. Any tests are very
welcome.
Cc: Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>
Cc: Stephen Rothwell <sfr@...hwell.id.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mips@...r.kernel.org
Cc: linux-serial@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Serge Semin (4):
mips: cm: Add __mips_cm_l2sync_phys_base prototype declaration
mips: cm: Add CM GCR and L2-sync base address getters declarations
mips: zboot: Fix "no previous prototype" build warning
tty: mips_ejtag_fdc: Fix passing incompatible pointer type warning
arch/mips/boot/compressed/uart-16550.c | 2 ++
arch/mips/boot/compressed/uart-alchemy.c | 2 ++
arch/mips/boot/compressed/uart-prom.c | 2 ++
arch/mips/include/asm/mips-cm.h | 16 ++++++++++++++++
arch/mips/kernel/mips-cm.c | 2 +-
drivers/tty/mips_ejtag_fdc.c | 2 +-
6 files changed, 24 insertions(+), 2 deletions(-)
--
2.43.0
Powered by blists - more mailing lists