Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sun, 11 Sep 2022 00:48:59 +0200
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.0
Message-ID: <20220910224858.GA13203@alpha.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:

  Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.0_1

for you to fetch changes up to 727488e305b223ca69205ca5a3b99ace21bbbf5f:

  mips: Select SPARSEMEM_EXTREME (2022-09-09 17:37:27 +0200)

----------------------------------------------------------------
- fix for loongson32 starup hang
- fix for octeon irq setup problem
- fix compiler warning for new CONFIG option
- switch to SPARSEMEM_EXTREME for all platforms selecting SPARSEMEM

----------------------------------------------------------------
Alexander Sverdlin (3):
      MIPS: octeon: Get rid of preprocessor directives around RESERVE32
      MIPS: OCTEON: irq: Fix octeon_irq_force_ciu_mapping()
      mips: Select SPARSEMEM_EXTREME

Yang Ling (1):
      MIPS: loongson32: ls1c: Fix hang during startup

 arch/mips/Kconfig                                  |  1 -
 arch/mips/cavium-octeon/executive/cvmx-cmd-queue.c |  4 ----
 arch/mips/cavium-octeon/octeon-irq.c               | 10 ++++++++
 arch/mips/cavium-octeon/setup.c                    | 27 +++++++++-------------
 arch/mips/loongson32/ls1c/board.c                  |  1 -
 5 files changed, 21 insertions(+), 22 deletions(-)

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