linux-kernel - [GIT PULL] MIPS fixes for v5.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201117180154.GA21834@alpha.franken.de>
Date:   Tue, 17 Nov 2020 19:01:54 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     torvalds@...ux-foundation.org
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] MIPS fixes for v5.10

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 ]