public inbox for linux-mips@vger.kernel.org
 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 changes for v6.19
Date: Tue, 9 Dec 2025 13:05:03 +0100	[thread overview]
Message-ID: <aTgQb7d1YDZCk3IQ@alpha.franken.de> (raw)

The following changes since commit 7d0a66e4bb9081d75c82ec4957c50034cb0ea449:

  Linux 6.18 (2025-11-30 14:42:10 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_6.19

for you to fetch changes up to 2b6d718c8dbe61aedffd7d12cf7bc60fab6f3d0e:

  MIPS: Fix whitespace damage in r4k_wait from VS timer fix (2025-12-01 10:34:34 +0100)

----------------------------------------------------------------
just cleanups and fixes

----------------------------------------------------------------
Dmitry Torokhov (1):
      MIPS: alchemy: mtx1: switch to static device properties

Gregory CLEMENT (2):
      MIPS: Fix HOTPLUG_PARALLEL dependency
      MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits

Keguang Zhang (1):
      mips: configs: loongson1: Update defconfig

Maciej W. Rozycki (1):
      MIPS: Fix whitespace damage in r4k_wait from VS timer fix

Rob Herring (Arm) (1):
      MIPS: dts: Always descend vendor subdirectories

Vishal Moola (Oracle) (1):
      mips: Remove __GFP_HIGHMEM masking

Yury Norov (1):
      mips: kvm: simplify kvm_mips_deliver_interrupts()

 arch/mips/Kconfig                     |   2 +-
 arch/mips/alchemy/board-mtx1.c        | 181 +++++++++++++++++++++++-----------
 arch/mips/boot/dts/Makefile           |  35 +++----
 arch/mips/boot/dts/realtek/Makefile   |   4 +-
 arch/mips/configs/loongson1_defconfig |  16 ++-
 arch/mips/include/asm/pgalloc.h       |   3 +-
 arch/mips/kernel/ftrace.c             |  25 ++++-
 arch/mips/kernel/genex.S              |   8 +-
 arch/mips/kvm/interrupt.c             |  20 +---
 9 files changed, 178 insertions(+), 116 deletions(-)

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

             reply	other threads:[~2025-12-09 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 12:05 Thomas Bogendoerfer [this message]
2025-12-09 21:21 ` [GIT PULL] MIPS changes for v6.19 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=aTgQb7d1YDZCk3IQ@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