From: Nishanth Menon <nm@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Swapnil Jakhade <sjakhade@cadence.com>,
Jyri Sarha <jsarha@ti.com>, Yuti Amonkar <yamonkar@cadence.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Tero Kristo <t-kristo@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs
Date: Mon, 26 Oct 2020 14:08:08 -0500 [thread overview]
Message-ID: <20201026190808.im4nb32jn4rd3xhu@crayon> (raw)
In-Reply-To: <d741c4d0-9e76-99de-7081-10f3a7a5cb1a@ti.com>
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://patchwork.kernel.org/project/linux-arm-kernel/patch/20201026165441.22894-1-nm@ti.com/
>
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.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2020-10-26 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 17:06 [PATCH] soc: ti: Kconfig: Drop ARM64 SoC specific configs Nishanth Menon
2020-10-26 18:00 ` Lokesh Vutla
2020-10-26 19:08 ` Nishanth Menon [this message]
2020-10-27 15:59 ` Lokesh Vutla
2020-10-27 16:23 ` Nishanth Menon
2020-11-12 21:56 ` Nishanth Menon
2020-11-12 21:59 ` santosh.shilimkar
2020-11-12 22:22 ` Nishanth Menon
2020-11-13 1:13 ` santosh.shilimkar
2020-11-13 2:47 ` 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=20201026190808.im4nb32jn4rd3xhu@crayon \
--to=nm@ti.com \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sjakhade@cadence.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=yamonkar@cadence.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;
as well as URLs for NNTP newsgroup(s).