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: Sat, 1 Feb 2025 22:19:23 +0100 [thread overview]
Message-ID: <Z56P2zOAU8Sjm1a9@alpha.franken.de> (raw)
The following changes since commit df1b8d6e89db0edd572a1e375f5d3dd5575b9a9b:
MIPS: pci-legacy: Override pci_address_to_pio (2025-01-20 20:39:23 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_6.14_1
for you to fetch changes up to ec918a11e63856999b31705e81226dd7dc043e20:
Revert "mips: fix shmctl/semctl/msgctl syscall for o32" (2025-01-31 09:28:38 +0100)
----------------------------------------------------------------
Revert commit breaking sysv ipc for o32 ABI
----------------------------------------------------------------
Thomas Bogendoerfer (1):
Revert "mips: fix shmctl/semctl/msgctl syscall for o32"
arch/mips/kernel/syscalls/syscall_o32.tbl | 6 +++---
1 file changed, 3 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:[~2025-02-01 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 21:19 Thomas Bogendoerfer [this message]
2025-02-01 23:25 ` [GIT PULL] MIPS fixes for v6.14 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 9:38 Thomas Bogendoerfer
2025-02-16 18:58 ` pr-tracker-bot
2025-03-02 8:48 Thomas Bogendoerfer
2025-03-02 12:38 ` 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=Z56P2zOAU8Sjm1a9@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