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.14
Date: Sun, 16 Feb 2025 10:38:28 +0100 [thread overview]
Message-ID: <Z7GyFB5hAays_aII@alpha.franken.de> (raw)
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.14_1
for you to fetch changes up to 733a90561ad0a4a74035d2d627098da85d43b592:
MIPS: fix mips_get_syscall_arg() for o32 (2025-02-13 12:41:29 +0100)
----------------------------------------------------------------
Fix for o32 ptrace/get_syscall_info
----------------------------------------------------------------
Dmitry V. Levin (1):
MIPS: fix mips_get_syscall_arg() for o32
Maciej W. Rozycki (1):
MIPS: Export syscall stack arguments properly for remote use
arch/mips/include/asm/ptrace.h | 4 ++--
arch/mips/include/asm/syscall.h | 32 ++++++++------------------------
arch/mips/kernel/asm-offsets.c | 6 ++++++
arch/mips/kernel/scall32-o32.S | 8 ++++----
4 files changed, 20 insertions(+), 30 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-02-16 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 9:38 Thomas Bogendoerfer [this message]
2025-02-16 18:58 ` [GIT PULL] MIPS fixes for v6.14 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 8:48 Thomas Bogendoerfer
2025-03-02 12:38 ` pr-tracker-bot
2025-02-01 21:19 Thomas Bogendoerfer
2025-02-01 23:25 ` 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=Z7GyFB5hAays_aII@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.