mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zenghui Yu <yuzenghui@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>, <soc@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <will@kernel.org>,
	<wanghaibin.wang@huawei.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] arm64: defconfig: drop obsolete ARCH_* configs
Date: Thu, 7 Oct 2021 18:24:24 +0800	[thread overview]
Message-ID: <1ebc899f-b7d7-fff4-9204-a0edd2be4387@huawei.com> (raw)
In-Reply-To: <YV7HGniKSKe7nXp/@arm.com>

On 2021/10/7 18:08, Catalin Marinas wrote:
> On Thu, Oct 07, 2021 at 05:42:46PM +0800, Zenghui Yu wrote:
>> On 2021/8/23 21:01, Krzysztof Kozlowski wrote:
>>> On 21/08/2021 05:05, Zenghui Yu wrote:
>>>> Per commit 4a9a1a5602d8 ("arm64: socfpga: merge Agilex and N5X into
>>>> ARCH_INTEL_SOCFPGA") and commit 89d4f98ae90d ("ARM: remove zte zx
>>>> platform"), they can be dropped from defconfig now.
>>>>
>>>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>>> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
>>>> ---
>>>>  arch/arm64/configs/defconfig | 3 ---
>>>>  1 file changed, 3 deletions(-)
>>>
>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>>
>> I have no idea about which tree should this patch go via, so a gentle
>> ping here. I've verified that this can still be applied cleanly on top
>> of today's -next.
> 
> Usually defconfig changes go in via the arm-soc tree rather than the
> arm64 one.

Thanks for the pointer!

[+ soc@kernel.org]

Zenghui

  reply	other threads:[~2021-10-07 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-21  3:05 Zenghui Yu
2021-08-23 13:01 ` Krzysztof Kozlowski
2021-10-07  9:42   ` Zenghui Yu
2021-10-07 10:08     ` Catalin Marinas
2021-10-07 10:24       ` Zenghui Yu [this message]
2021-10-07 13:14         ` Arnd Bergmann

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=1ebc899f-b7d7-fff4-9204-a0edd2be4387@huawei.com \
    --to=yuzenghui@huawei.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=wanghaibin.wang@huawei.com \
    --cc=will@kernel.org \
    /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®