On 13:59-20201112, santosh.shilim...@oracle.com wrote:
> 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...@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...@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.

OK, sounds fine to me, If you can give me a tag, I can add queue up
defconfig on top to prevent bisect issues.

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

Reply via email to