linux-kernel - Re: [PATCH 2/2] Revert "MIPS: unhide PATA

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

Message-ID: <20230609082158.GF8160@alpha.franken.de>
Date:   Fri, 9 Jun 2023 10:21:58 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     "Maciej W. Rozycki" <macro@...am.me.uk>
Cc:     Manuel Lauss <manuel.lauss@...il.com>, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Revert "MIPS: unhide PATA_PLATFORM"

On Thu, Jun 01, 2023 at 01:56:36PM +0100, Maciej W. Rozycki wrote:
> Revert commit 75b18aac6fa3 ("MIPS: unhide PATA_PLATFORM") now that 
> HAVE_PATA_PLATFORM is set selectively for all the relevant platforms.
> 
> Verified with `db1xxx_defconfig' and `sb1250_swarm_defconfig' by making 
> sure PATA_PLATFORM is still there in `.config' with this change applied, 
> and with `malta_defconfig' by making sure it's now gone.
> 
> Signed-off-by: Maciej W. Rozycki <macro@...am.me.uk>
> ---
>  arch/mips/Kconfig |    1 -
>  1 file changed, 1 deletion(-)
> 
> linux-mips-no-pata-platform.diff
> Index: linux-macro/arch/mips/Kconfig
> ===================================================================
> --- linux-macro.orig/arch/mips/Kconfig
> +++ linux-macro/arch/mips/Kconfig
> @@ -79,7 +79,6 @@ config MIPS
>  	select HAVE_LD_DEAD_CODE_DATA_ELIMINATION
>  	select HAVE_MOD_ARCH_SPECIFIC
>  	select HAVE_NMI
> -	select HAVE_PATA_PLATFORM
>  	select HAVE_PERF_EVENTS
>  	select HAVE_PERF_REGS
>  	select HAVE_PERF_USER_STACK_DUMP

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 ]