mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Davis" <afd@ti.com>, "Nishanth Menon" <nm@ti.com>
Cc: "Russell King" <linux@armlinux.org.uk>,
	"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 20:56:26 +0100	[thread overview]
Message-ID: <3cc8741e-6866-4068-9226-d46b68b7c801@app.fastmail.com> (raw)
In-Reply-To: <5f5a2ecd-7878-46ba-9a85-a2a4ba060ad7@ti.com>

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

  reply	other threads:[~2024-01-24 19:56 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
2024-01-24 18:52         ` Andrew Davis
2024-01-24 19:56           ` Arnd Bergmann [this message]
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=3cc8741e-6866-4068-9226-d46b68b7c801@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=afd@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=nm@ti.com \
    --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

all inboxes | Powered by JetHome®