Received-SPF: pass (google.com: domain of linux-kernel+bounces-37343-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Wed, 24 Jan 2024 10:41:16 -0600
From: Nishanth Menon <nm@ti.com>
To: Andrew Davis <afd@ti.com>
CC: Russell King <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
        Vignesh Raghavendra <vigneshr@ti.com>,
        Santosh Shilimkar
	<ssantosh@kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: configs: keystone: Remove this defconfig
Message-ID: <20240124164116.k5ah56xvuclfkxdr@despise>
References: <20240124162857.111915-1-afd@ti.com>
 <20240124162857.111915-2-afd@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20240124162857.111915-2-afd@ti.com>

On 10:28-20240124, Andrew Davis wrote:
> TI Keystone devices can and should use the common multi-v7 defconfig.
> Currently it is not clear which defconfig should be used and so config
> options for Keystone boards are added to either both defconfigs, or only
> one or the other. As nice as it is to have a config just for this platform
> it is a maintenance burden. As it is not used by generic distros it is not
> very useful to continue to maintain. Remove this defconfig.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
>  arch/arm/configs/keystone_defconfig | 238 ----------------------------
>  1 file changed, 238 deletions(-)
>  delete mode 100644 arch/arm/configs/keystone_defconfig
> 

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.

I know we had intent on multi_v7_defconfig -> but as far as I recollect,
at least during armv7 it did'nt exactly pan out as it did on armv8.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D