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 v5.16
Date: Sat, 27 Nov 2021 10:43:17 +0100 [thread overview]
Message-ID: <20211127094317.GA6302@alpha.franken.de> (raw)
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_5.16_2
for you to fetch changes up to 41ce097f714401e6ad8f3f5eb30d7f91b0b5e495:
MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48 (2021-11-25 16:52:11 +0100)
----------------------------------------------------------------
- build fix for ZSTD enabled configs
- fix for preempt warning
- fix for loongson FTLB detection
- fix for page table level selection
----------------------------------------------------------------
Huang Pei (2):
MIPS: loongson64: fix FTLB configuration
MIPS: use 3-level pgtable for 64KB page size on MIPS_VA_BITS_48
Paul Cercueil (1):
MIPS: boot/compressed/: add __ashldi3 to target for ZSTD compression
Tiezhu Yang (1):
MIPS: Fix using smp_processor_id() in preemptible in show_cpuinfo()
arch/mips/Kconfig | 2 +-
arch/mips/boot/compressed/Makefile | 2 +-
arch/mips/kernel/cpu-probe.c | 4 ++--
arch/mips/kernel/proc.c | 2 +-
4 files changed, 5 insertions(+), 5 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:[~2021-11-27 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 9:43 Thomas Bogendoerfer [this message]
2021-11-27 18:58 ` [GIT PULL] MIPS fixes for v5.16 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-12-19 10:54 Thomas Bogendoerfer
2021-12-19 20:34 ` pr-tracker-bot
2021-11-17 22:11 Thomas Bogendoerfer
2021-11-17 23:58 ` 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=20211127094317.GA6302@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;
as well as URLs for NNTP newsgroup(s).