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.8
Date: Wed, 14 Feb 2024 17:54:46 +0100 [thread overview]
Message-ID: <ZczwVtJLAl+aeunp@alpha.franken.de> (raw)
The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:
Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.8_2
for you to fetch changes up to 8fa5070833886268e4fb646daaca99f725b378e9:
mm/memory: Use exception ip to search exception tables (2024-02-12 23:04:42 +0100)
----------------------------------------------------------------
- Fix for broken ipv6 checksums
- Fix handling of exceptions in delay slots
----------------------------------------------------------------
Guenter Roeck (1):
MIPS: Add 'memory' clobber to csum_ipv6_magic() inline assembler
Jiaxun Yang (3):
ptrace: Introduce exception_ip arch hook
MIPS: Clear Cause.BD in instruction_pointer_set
mm/memory: Use exception ip to search exception tables
arch/mips/include/asm/checksum.h | 3 ++-
arch/mips/include/asm/ptrace.h | 3 +++
arch/mips/kernel/ptrace.c | 7 +++++++
include/linux/ptrace.h | 4 ++++
mm/memory.c | 4 ++--
5 files changed, 18 insertions(+), 3 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:[~2024-02-14 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:54 Thomas Bogendoerfer [this message]
2024-02-15 0:12 ` [GIT PULL] MIPS fixes for v6.8 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-01-28 13:28 Thomas Bogendoerfer
2024-01-28 18:46 ` Linus Torvalds
2024-01-28 18:47 ` 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=ZczwVtJLAl+aeunp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.