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: <20200416164016.GE24743@alpha.franken.de>
Date:   Thu, 16 Apr 2020 18:40:16 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     sboyd@...nel.org, jiaxun.yang@...goat.com,
        linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, chenhc@...ote.com,
        Paul Burton <paulburton@...nel.org>, mturquette@...libre.com
Subject: Re: [PATCH] mips: loongsoon2ef: remove private clk api

On Thu, Apr 09, 2020 at 11:02:28AM +0200, Arnd Bergmann wrote:
> As platforms are moving to COMMON_CLK in general, loongson2ef
> stuck out as something that has a private implementation but
> does not actually use it except for setting the frequency of
> the CPU itself from the loongson2_cpufreq driver.
> 
> Change that driver to call the register setting function directly
> and remove the rest of the stub implementation.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
>  arch/mips/include/asm/clock.h                 | 49 ----------
>  .../include/asm/mach-loongson2ef/loongson.h   |  1 +
>  arch/mips/loongson2ef/Kconfig                 |  1 -
>  arch/mips/loongson2ef/lemote-2f/clock.c       | 98 +------------------
>  arch/mips/loongson64/smp.c                    |  1 -
>  drivers/cpufreq/loongson2_cpufreq.c           | 22 +----
>  6 files changed, 8 insertions(+), 164 deletions(-)
>  delete mode 100644 arch/mips/include/asm/clock.h

applied to mips-next.

Thomas.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ