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
Date: Sun, 11 Sep 2022 00:48:59 +0200 [thread overview]
Message-ID: <20220910224858.GA13203@alpha.franken.de> (raw)
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 ]
next reply other threads:[~2022-09-10 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 22:48 Thomas Bogendoerfer [this message]
2022-09-11 19:36 ` [GIT PULL] MIPS fixes for v6.0 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-09-21 13:35 Thomas Bogendoerfer
2022-09-21 16:34 ` 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=20220910224858.GA13203@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