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.10
Date: Tue, 17 Nov 2020 19:01:54 +0100 [thread overview]
Message-ID: <20201117180154.GA21834@alpha.franken.de> (raw)
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_fixes_5.10_1
for you to fetch changes up to ac3b57adf87ad9bac7e33ca26bbbb13fae1ed62b:
MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu (2020-11-17 12:53:57 +0100)
----------------------------------------------------------------
- fix bug preventing booting on several platforms
- fix for build error, when modules need has_transparent_hugepage
- fix for memleak in alchemy clk setup
----------------------------------------------------------------
Randy Dunlap (1):
MIPS: export has_transparent_hugepage() for modules
Thomas Bogendoerfer (1):
MIPS: kernel: Fix for_each_memblock conversion
Zhang Qilong (1):
MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
arch/mips/alchemy/common/clock.c | 9 ++++++++-
arch/mips/kernel/setup.c | 6 +++---
arch/mips/mm/tlb-r4k.c | 1 +
3 files changed, 12 insertions(+), 4 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:[~2020-11-17 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:01 Thomas Bogendoerfer [this message]
2020-11-17 19:34 ` [GIT PULL] MIPS fixes for v5.10 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=20201117180154.GA21834@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