[GIT PULL] MIPS changes for v6.12

From: Thomas Bogendoerfer
Date: Thu Sep 12 2024 - 05:56:15 EST


The following changes since commit 5be63fc19fcaa4c236b307420483578a56986a37:

Linux 6.11-rc5 (2024-08-25 19:07:11 +1200)

are available in the Git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_6.12

for you to fetch changes up to 439667fb943cfea46d7bde5c7b29c89efec3cbc7:

mips: Remove posix_types.h include from sigcontext.h (2024-08-29 10:46:00 +0200)

----------------------------------------------------------------
- use devm_clk_get_enabled() helper
- prototype fixes
- cleanup unused stuff

----------------------------------------------------------------
Gaosheng Cui (6):
MIPS: Remove unused function dump_au1000_dma_channel() in dma.c
mips/jazz: remove unused jazz_handle_int() declaration
MIPS: MT: Remove unused function mips_mt_regdump()
MIPS: Remove unused declarations in asm/cmp.h
MIPS: Remove unused mips_display/_scroll_message() declarations
MIPS: dec: prom: Remove unused unregister_prom_console() declaration

Vincent Legoll (2):
MIPS: ralink: Fix missing `plat_time_init` prototype
MIPS: ralink: Fix missing `get_c0_perfcount_int` prototype

Wu Bo (2):
bus: bt1-axi: change to use devm_clk_get_enabled() helper
bus: bt1-apb: change to use devm_clk_get_enabled() helper

Xi Ruoyao (1):
mips: Remove posix_types.h include from sigcontext.h

arch/mips/alchemy/common/dma.c | 23 --------
arch/mips/include/asm/cmp.h | 8 ---
arch/mips/include/asm/dec/prom.h | 1 -
arch/mips/include/asm/mach-au1x00/au1000_dma.h | 1 -
arch/mips/include/asm/mips-boards/generic.h | 3 -
arch/mips/include/asm/mips_mt.h | 2 -
arch/mips/include/uapi/asm/sigcontext.h | 1 -
arch/mips/jazz/setup.c | 2 -
arch/mips/kernel/mips-mt.c | 77 --------------------------
arch/mips/ralink/irq-gic.c | 1 +
arch/mips/ralink/timer-gic.c | 2 +
drivers/bus/bt1-apb.c | 23 +-------
drivers/bus/bt1-axi.c | 23 +-------
13 files changed, 6 insertions(+), 161 deletions(-)

--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]