public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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
Date: Wed, 24 Jan 2024 12:04:51 -0600	[thread overview]
Message-ID: <20240124180451.bptuhldi44leulr3@pectin> (raw)
In-Reply-To: <0ab47165-3ba3-4d34-aea0-9bc12fd5ff31@ti.com>

On 11:31-20240124, Andrew Davis wrote:
> On 1/24/24 10:41 AM, Nishanth Menon wrote:
> > 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.
> > 
> 
> 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.

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-01-24 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 16:28 [PATCH 1/2] ARM: multi_v7_defconfig: Add more TI Keystone support Andrew Davis
2024-01-24 16:28 ` [PATCH 2/2] ARM: configs: keystone: Remove this defconfig Andrew Davis
2024-01-24 16:41   ` Nishanth Menon
2024-01-24 17:31     ` Andrew Davis
2024-01-24 18:04       ` Nishanth Menon [this message]
2024-01-24 18:52         ` Andrew Davis
2024-01-24 19:56           ` Arnd Bergmann
2024-01-25 13:41             ` Nishanth Menon
2024-01-24 16:41 ` [PATCH 1/2] ARM: multi_v7_defconfig: Add more TI Keystone support Nishanth Menon
2024-01-24 16:59   ` Andrew Davis
2024-01-24 17:21     ` Nishanth Menon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240124180451.bptuhldi44leulr3@pectin \
    --to=nm@ti.com \
    --cc=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ssantosh@kernel.org \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox