From: Arnd Bergmann <arnd@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Will Deacon <will.deacon@arm.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
Wei Xu <xuwei5@hisilicon.com>,
devicetree <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/4] ARM: hisi: add support for Kunpeng50x SoC
Date: Mon, 1 Feb 2021 09:35:34 +0100 [thread overview]
Message-ID: <CAK8P3a142CkJ0kOD6mK+H-E2NrKZ6Ec-aYasddAUmAhTWhrjcA@mail.gmail.com> (raw)
In-Reply-To: <20210201033601.1642-3-thunder.leizhen@huawei.com>
On Mon, Feb 1, 2021 at 4:35 AM Zhen Lei <thunder.leizhen@huawei.com> wrote:
>
> Enable support for the Hisilicon Kunpeng506 and Kunpeng509 SoC.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Russell, do you have a preference for how to get this series merged
after the last comments are resolved?
I think there is no technical problem in having patch two merged through
the soc tree, while merging the other three through your tree, but it
seems more logical to keep all four together in either location.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Will Deacon <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Wei Xu <xuwei5@hisilicon.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 2/4] ARM: hisi: add support for Kunpeng50x SoC
Date: Mon, 1 Feb 2021 09:35:34 +0100 [thread overview]
Message-ID: <CAK8P3a142CkJ0kOD6mK+H-E2NrKZ6Ec-aYasddAUmAhTWhrjcA@mail.gmail.com> (raw)
In-Reply-To: <20210201033601.1642-3-thunder.leizhen@huawei.com>
On Mon, Feb 1, 2021 at 4:35 AM Zhen Lei <thunder.leizhen@huawei.com> wrote:
>
> Enable support for the Hisilicon Kunpeng506 and Kunpeng509 SoC.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Russell, do you have a preference for how to get this series merged
after the last comments are resolved?
I think there is no technical problem in having patch two merged through
the soc tree, while merging the other three through your tree, but it
seems more logical to keep all four together in either location.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-01 8:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 3:35 [PATCH v6 0/4] ARM: Add support for Hisilicon Kunpeng L3 cache controller Zhen Lei
2021-02-01 3:35 ` Zhen Lei
2021-02-01 3:35 ` [PATCH v6 1/4] ARM: LPAE: Use phys_addr_t instead of unsigned long in outercache hooks Zhen Lei
2021-02-01 3:35 ` Zhen Lei
2021-02-01 3:35 ` [PATCH v6 2/4] ARM: hisi: add support for Kunpeng50x SoC Zhen Lei
2021-02-01 3:35 ` Zhen Lei
2021-02-01 8:35 ` Arnd Bergmann [this message]
2021-02-01 8:35 ` Arnd Bergmann
2021-02-01 11:49 ` Leizhen (ThunderTown)
2021-02-01 11:49 ` Leizhen (ThunderTown)
2021-02-01 12:14 ` Arnd Bergmann
2021-02-01 12:14 ` Arnd Bergmann
2021-02-01 3:36 ` [PATCH v6 3/4] dt-bindings: arm: hisilicon: Add binding for Kunpeng L3 cache controller Zhen Lei
2021-02-01 3:36 ` Zhen Lei
2021-02-01 3:36 ` [PATCH v6 4/4] ARM: Add support for Hisilicon " Zhen Lei
2021-02-01 3:36 ` Zhen Lei
2021-02-01 8:31 ` Arnd Bergmann
2021-02-01 8:31 ` Arnd Bergmann
2021-02-01 11:38 ` Leizhen (ThunderTown)
2021-02-01 11:38 ` Leizhen (ThunderTown)
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=CAK8P3a142CkJ0kOD6mK+H-E2NrKZ6Ec-aYasddAUmAhTWhrjcA@mail.gmail.com \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=thunder.leizhen@huawei.com \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.