linux-kernel - Re: [PATCH 2/2] ARM: configs: keystone: Remove this defconfig

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: <3cc8741e-6866-4068-9226-d46b68b7c801@app.fastmail.com>
Date: Wed, 24 Jan 2024 20:56:26 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Andrew Davis" <afd@...com>, "Nishanth Menon" <nm@...com>
Cc: "Russell King" <linux@...linux.org.uk>,
 "Vignesh Raghavendra" <vigneshr@...com>,
 "Santosh Shilimkar" <ssantosh@...nel.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ARM: configs: keystone: Remove this defconfig

On Wed, Jan 24, 2024, at 19:52, Andrew Davis wrote:
> On 1/24/24 12:04 PM, Nishanth Menon wrote:
>> On 11:31-20240124, Andrew Davis wrote:
>>> On 1/24/24 10:41 AM, Nishanth Menon wrote:
>>>>
>>>> There are a bunch of downstream folks who will have recipe fails etc if
>>>> we do that. I am not sure we need to go down that route.
>>>>
>>>
>>> That is the point of this patch, we want to stop any remaining downstream
>>> folks from using this defconfig. It is not maintained nor updated like
>>> the multi_v7_defconfig, any new or needed options will only be added to
>>> multi-v7 defconfig.
>>>
>> 
>> I am going to have to defer to ARM maintainers what they think..
>> enabling LPAE etc in common multi_v7_config.
>> 
>
> We are not enabling LPAE in common multi_v7_config, that can't be
> done as many plats do not support it. Keystone will use the new
> multi_v7_lpae_defconfig which was just added:
>
> e9faf9b0b07a ("ARM: add multi_v7_lpae_defconfig")
>
> That is what prompted me to make this change, we now have a
> commonish config that works for Keystone.

I think adding keystone to multi_v7_defconfig is a good
idea here for the reasons you explained. I don't mind keeping
the other one around as well though, since keystone is
a bit special.

     Arnd