From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes for v6.15
Date: Sun, 11 May 2025 09:34:34 +0200 [thread overview]
Message-ID: <aCBTCo8kyo-LxpV5@alpha.franken.de> (raw)
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.15_1
for you to fetch changes up to c44572e0cc13c9afff83fd333135a0aa9b27ba26:
MIPS: Fix MAX_REG_OFFSET (2025-04-30 20:04:59 +0200)
----------------------------------------------------------------
Fix delayed timers
Fix NULL pointer deref
Fix wrong range check
----------------------------------------------------------------
Marco Crivellari (3):
MIPS: Fix idle VS timer enqueue
MIPS: Move r4k_wait() to .cpuidle.text section
MIPS: rename rollback_handler with skipover_handler
Thorsten Blum (2):
MIPS: CPS: Fix potential NULL pointer dereferences in cps_prepare_cpus()
MIPS: Fix MAX_REG_OFFSET
arch/mips/include/asm/idle.h | 5 ++-
arch/mips/include/asm/ptrace.h | 3 +-
arch/mips/kernel/genex.S | 71 ++++++++++++++++++++++++------------------
arch/mips/kernel/idle.c | 7 -----
arch/mips/kernel/smp-cps.c | 4 +++
arch/mips/kernel/traps.c | 10 +++---
6 files changed, 54 insertions(+), 46 deletions(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2025-05-11 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 7:34 Thomas Bogendoerfer [this message]
2025-05-11 18:40 ` [GIT PULL] MIPS fixes for v6.15 pr-tracker-bot
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=aCBTCo8kyo-LxpV5@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=torvalds@linux-foundation.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