public inbox for linux-kernel@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 part 2 for v6.11
Date: Thu, 25 Jul 2024 18:09:56 +0200	[thread overview]
Message-ID: <ZqJ41Aiswy5guHm/@alpha.franken.de> (raw)

The following changes since commit bb2d63500b5c8fd1ea425caffe2d44c931fefc6b:

  MIPS: config: Add ip30_defconfig (2024-07-15 18:17:34 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 2c716cf17edee74424336e87fe42b99ee5e91bad:

  mips: sibyte: add missing MODULE_DESCRIPTION() macro (2024-07-23 09:47:40 +0200)

----------------------------------------------------------------
- Use improved timer sync for Loongson64
- Fix address of GCR_ACCESS register
- Add missing MODULE_DESCRIPTION

----------------------------------------------------------------
Gregory CLEMENT (1):
      MIPS: SMP-CPS: Fix address for GCR_ACCESS register for CM3 and later

Jeff Johnson (1):
      mips: sibyte: add missing MODULE_DESCRIPTION() macro

Jiaxun Yang (1):
      MIPS: Loongson64: Switch to SYNC_R4K

 arch/mips/Kconfig                   |  1 +
 arch/mips/include/asm/mips-cm.h     |  4 ++++
 arch/mips/include/asm/smp.h         |  1 -
 arch/mips/kernel/smp-cps.c          |  5 ++++-
 arch/mips/loongson64/smp.c          | 35 ++---------------------------------
 arch/mips/sibyte/common/sb_tbprof.c |  1 +
 6 files changed, 12 insertions(+), 35 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-07-25 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 16:09 Thomas Bogendoerfer [this message]
2024-07-25 20:37 ` [GIT PULL] MIPS changes part 2 for v6.11 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=ZqJ41Aiswy5guHm/@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