Linux MIPS Architecture development
 help / color / mirror / Atom feed
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.10
Date: Sun, 23 Jun 2024 12:09:49 +0200	[thread overview]
Message-ID: <Znf0bReGRC9C1ACk@alpha.franken.de> (raw)

The following changes since commit 6e5aee08bd2517397c9572243a816664f2ead547:

  Revert "MIPS: pci: lantiq: restore reset gpio polarity" (2024-06-13 10:17:09 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.10_2

for you to fetch changes up to 0d5679a0aae2d8cda72169452c32e5cb88a7ab33:

  mips: fix compat_sys_lseek syscall (2024-06-21 10:16:34 +0200)

----------------------------------------------------------------
- fix lseek in o32 compat mode
- fix for microMIPS MT ASE helpers

----------------------------------------------------------------
Arnd Bergmann (1):
      mips: fix compat_sys_lseek syscall

Jiaxun Yang (1):
      MIPS: mipsmtregs: Fix target register for MFTC0

 arch/mips/include/asm/mipsmtregs.h        | 2 +-
 arch/mips/kernel/syscalls/syscall_o32.tbl | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

             reply	other threads:[~2024-06-23 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 10:09 Thomas Bogendoerfer [this message]
2024-06-23 15:13 ` [GIT PULL] MIPS fixes for v6.10 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-06-19 11:07 Thomas Bogendoerfer
2024-06-19 17:33 ` 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=Znf0bReGRC9C1ACk@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