[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b23cb5b-b1c9-34b9-2bdf-4f9c2df9ad0d@oracle.com>
Date: Thu, 12 Nov 2020 13:59:59 -0800
From: santosh.shilimkar@...cle.com
To: Nishanth Menon <nm@...com>, Lokesh Vutla <lokeshvutla@...com>
Cc: Peter Ujfalusi <peter.ujfalusi@...com>,
Yuti Amonkar <yamonkar@...ence.com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Sekhar Nori <nsekhar@...com>, linux-kernel@...r.kernel.org,
Jyri Sarha <jsarha@...com>, Tero Kristo <t-kristo@...com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Swapnil Jakhade <sjakhade@...ence.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs
On 11/12/20 1:56 PM, Nishanth Menon wrote:
> On 14:08-20201026, Nishanth Menon wrote:
>> On 23:30-20201026, Lokesh Vutla wrote:
>> [..]
>>> ➜ linux git:(master) git grep -in ARCH_K3_AM6_SOC
>>> arch/arm64/configs/defconfig:961:CONFIG_ARCH_K3_AM6_SOC=y
>>> drivers/soc/ti/Kconfig:7:config ARCH_K3_AM6_SOC
>>> ➜ linux git:(master) git grep -in ARCH_K3_J721E_SOC
>>> arch/arm64/configs/defconfig:962:CONFIG_ARCH_K3_J721E_SOC=y
>>> drivers/gpu/drm/bridge/cadence/Kconfig:16: depends on ARCH_K3_J721E_SOC ||
>>> COMPILE_TEST
>>> drivers/soc/ti/Kconfig:12:config ARCH_K3_J721E_SOC
>>>
>>>
>>> I see drm bridge Kconfig is cleaned[0]. Please clean the defconfig as well.
>>>
>>> [0]
>>> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-arm-kernel/patch/20201026165441.22894-1-nm@ti.com/__;!!GqivPVa7Brio!KWOx2aLl7hlHQrN--kiz1N5WaPWgeZzFZ12ptg8NzJE2BSnxxrWmsoqn5vjMvpfO1bSGYQ$
>>>
>>
>> Yes, the defconfig patches have to be queued up in a different queue,
>> Lets see where the two patches fall and will post the defconfig
>> updates as well.
>
>
> Santosh,
>
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-arm-kernel/patch/20201026165441.22894-1-nm@ti.com/__;!!GqivPVa7Brio!KWOx2aLl7hlHQrN--kiz1N5WaPWgeZzFZ12ptg8NzJE2BSnxxrWmsoqn5vjMvpfO1bSGYQ$
> looks available in next now.
>
> Can we queue this patch[1] up for 5.11 window?
>
> Depending on your preference, I can carry the defconfig patch[2] (to
> prevent merge dependencies, might be good to get an immutable tag) OR
> you can pick the defconfig patch up that cleans after removing the
> symbol.
>
I can apply SOC kconfig patch [1] to my soc branch. That branch with
some additional patches am going to send up, so it should
work. Let me know.
Regards,
Santosh
Powered by blists - more mailing lists