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 changes part 2 for v6.3
Date: Thu, 2 Mar 2023 16:21:23 +0100	[thread overview]
Message-ID: <20230302152123.GA11226@alpha.franken.de> (raw)

The following changes since commit 91dc288f4edf0d768e46c2c6d33e0ab703403459:

  MIPS: vpe-mt: drop physical_memsize (2023-02-20 15:11:01 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 1a2c73f4834dd79e4f2c590ac75358fb44137650:

  MIPS: Workaround clang inline compat branch issue (2023-02-28 23:09:49 +0100)

----------------------------------------------------------------
a few more cleanups/fixes

----------------------------------------------------------------
Arınç ÜNAL (2):
      mips: remove SYS_HAS_CPU_MIPS32_R1 from RALINK
      mips: ralink: make SOC_MT7621 select PINCTRL

Jiaxun Yang (4):
      MIPS: Remove DMA_PERDEV_COHERENT
      MIPS: smp-cps: Don't rely on CP0_CMGCRBASE
      MIPS: cevt-r4k: Offset the value used to clear compare interrupt
      MIPS: Workaround clang inline compat branch issue

Sergio Paracuellos (2):
      mips: dts: ralink: mt7621: rename watchdog node from 'wdt' into 'watchdog'
      mips: dts: ralink: mt7621: add phandle to system controller node for watchdog

 arch/mips/Kconfig                     | 10 ++++------
 arch/mips/boot/dts/ralink/mt7621.dtsi |  3 ++-
 arch/mips/include/asm/asm.h           |  2 +-
 arch/mips/include/asm/smp-cps.h       |  4 ++++
 arch/mips/kernel/cevt-r4k.c           |  4 ++--
 arch/mips/kernel/cps-vec.S            | 35 +++++++++++++++--------------------
 arch/mips/kernel/smp-cps.c            |  2 ++
 arch/mips/ralink/Kconfig              |  2 +-
 8 files changed, 31 insertions(+), 31 deletions(-)

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

             reply	other threads:[~2023-03-02 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 15:21 Thomas Bogendoerfer [this message]
2023-03-02 18:37 ` [GIT PULL] MIPS changes part 2 for v6.3 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=20230302152123.GA11226@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