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.18
Date: Sat, 29 Nov 2025 21:55:09 +0100 [thread overview]
Message-ID: <aStdrYiDwO05O1A_@alpha.franken.de> (raw)
The following changes since commit ac3fd01e4c1efce8f2c054cdeb2ddd2fc0fb150d:
Linux 6.18-rc7 (2025-11-23 14:53:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.18_2
for you to fetch changes up to 841ecc979b18d3227fad5e2d6a1e6f92688776b5:
MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow (2025-11-29 13:36:05 +0100)
----------------------------------------------------------------
Fix TLB unification for cores with more than 64 TLB entries
----------------------------------------------------------------
Thomas Bogendoerfer (1):
MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow
arch/mips/mm/tlb-r4k.c | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 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-11-29 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 20:55 Thomas Bogendoerfer [this message]
2025-11-29 23:23 ` [GIT PULL] MIPS fixes for v6.18 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-11-22 20:47 Thomas Bogendoerfer
2025-11-22 23:55 ` pr-tracker-bot
2025-11-24 15:46 ` Gregory CLEMENT
2025-11-24 21:06 ` Thomas Bogendoerfer
2025-11-24 21:53 ` Thomas Bogendoerfer
2025-11-25 7:32 ` Maciej W. Rozycki
2025-11-25 11:00 ` Thomas Bogendoerfer
2025-11-25 14:25 ` Maciej W. Rozycki
2025-11-25 10:10 ` Gregory CLEMENT
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=aStdrYiDwO05O1A_@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;
as well as URLs for NNTP newsgroup(s).