linux-kernel - Re: [PATCH 0/2] MIPS: SiByte: Update SWARM defconfig for PATA support

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]

Date:   Wed, 24 Mar 2021 11:02:04 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     "Maciej W. Rozycki" <macro@...am.me.uk>
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 0/2] MIPS: SiByte: Update SWARM defconfig for PATA support

On Sun, Mar 21, 2021 at 08:55:37PM +0100, Maciej W. Rozycki wrote:
> Hi,
> 
>  In the course of looking into Christoph's recent proposal to drop legacy 
> IDE drivers I have noticed that SiByte SWARM's defconfig does not enable 
> the pata_platform driver for the onboard PATA interface.  I think default 
> configuration ought to enable all the supported onboard devices unless 
> there are specific reasons so as not to, and the PATA interface is one of 
> the boot devices supported by the CFE firmware, so I think even more then 
> that it should be included by default.
> 
>  Change split into two because the defconfig has become stale since the 
> last update, so 1/2 first regenerates it, and then 2/2 applies the actual 
> modification.
> 
>  Sadly I'm currently away from my SWARM board for the foreseeable future 
> and I have no remote access to it either, but this is supposed not to need 
> run-time verification.  Build-tested only then.
> 
>  Please apply.

series 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 ]