linux-kernel - Re: [PATCH 1/2] MIPS: Loongson32: Remove reset.c

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230330113053.GB9674@alpha.franken.de>
Date:   Thu, 30 Mar 2023 13:30:53 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Keguang Zhang <keguang.zhang@...il.com>
Cc:     linux-watchdog@...r.kernel.org, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Yang Ling <gnaygnil@...il.com>
Subject: Re: [PATCH 1/2] MIPS: Loongson32: Remove reset.c

On Thu, Mar 30, 2023 at 06:20:12PM +0800, Keguang Zhang wrote:
> The Loongson-1 restart handler will be moved to watchdog driver,
> then _machine_restart is no longer needed.
> The _machine_halt and pm_power_off are also unnecessary,
> which contain no hardware operations.
> 
> Therefore, remove the entire reset.c and related header file.
> Update the Makefile accordingly.
> 
> Signed-off-by: Keguang Zhang <keguang.zhang@...il.com>
> ---
>  .../include/asm/mach-loongson32/regs-wdt.h    | 15 ------
>  arch/mips/loongson32/common/Makefile          |  2 +-
>  arch/mips/loongson32/common/reset.c           | 51 -------------------
>  3 files changed, 1 insertion(+), 67 deletions(-)
>  delete mode 100644 arch/mips/include/asm/mach-loongson32/regs-wdt.h
>  delete mode 100644 arch/mips/loongson32/common/reset.c

Acked-by: Thomas Bogendoerfer <tsbogend@...ha.franken.de>

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