From: "Arnd Bergmann" <arnd@arndb.de>
To: "Brian Masney" <bmasney@redhat.com>,
"Long Zhao" <zl020895@163.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: "Brian Masney" <masneyb@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Long Zhao" <longzhao@ambarella.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Jerome Brunet" <jbrunet@baylibre.com>,
linux-clk@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Linus Walleij" <linusw@kernel.org>
Subject: Re: [PATCH v11 0/5] arm64: add Ambarella CV75 SoC support
Date: Thu, 19 Nov 2026 09:46:02 +0100 [thread overview]
Message-ID: <d2cb7e5e-9c39-4534-9ed8-a5e2b6074dc1@app.fastmail.com> (raw)
In-Reply-To: <avslH10GRqkVT9fU@redhat.com>
On Mon, Nov 16, 2026, at 16:45, Brian Masney wrote:
> Hi Long (and Arnd/Krzysztof),
>
> On Mon, Nov 16, 2026 at 11:59:28AM +0800, zl020895 wrote:
>> At 2026-11-11 20:25:07, "Brian Masney" <masneyb@kernel.org> wrote:
>> >So how about this:
>> >
>> >- Have Long post a new version that splits out the creation of the new
>> > Kconfig symbol ARCH_AMBARELLA into it's own patch. I assume Arnd could
>> > provide an ACK on this?
>> >
>> >- I create an immutable branch that contains that the two dt-binding
>> > patches, plus the ARCH_AMBARELLA Kconfig patch.
>>
>> Just checking in -- there hasn't been further feedback from
>> Arnd/Krzysztof on the plan yet.
>>
>> Should I go ahead and prepare that split for v12, or hold
>> off until Arnd/Krzysztof chime in?
>
> I haven't heard back from Arnd/Krzysztof yet. How about wait 48 hours to
> see if they respond, and if they don't respond within that timeframe,
> then go ahead about post a v12 with the ARCH_AMBARELLA split out into
> it's own patch. I think that's a good change to make anyways.
Sorry about missing your question, this sounds fine to me.
Arnd
prev parent reply other threads:[~2026-11-19 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:06 Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 1/5] dt-bindings: arm: add Ambarella CV75 platforms Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 2/5] dt-bindings: clock: add Ambarella CV75 RCT Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 3/5] clk: ambarella: add CV75 RCT clock controller Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 4/5] arm64: ambarella: add ARCH_AMBARELLA and CV75 EVK DT Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 5/5] MAINTAINERS: add ARM/AMBARELLA SoC support Long Zhao via B4 Relay
2026-11-10 1:22 ` [PATCH v11 0/5] arm64: add Ambarella CV75 " Brian Masney
2026-11-10 8:02 ` Krzysztof Kozlowski
2026-11-10 8:23 ` Arnd Bergmann
2026-11-10 8:27 ` Krzysztof Kozlowski
2026-11-10 8:46 ` Arnd Bergmann
2026-11-10 12:24 ` Brian Masney
2026-11-10 14:11 ` Andy Shevchenko
2026-11-11 12:25 ` Brian Masney
2026-11-16 3:59 ` zl020895
2026-11-16 15:45 ` Brian Masney
2026-11-19 8:46 ` Arnd Bergmann [this message]
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=d2cb7e5e-9c39-4534-9ed8-a5e2b6074dc1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bmasney@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longzhao@ambarella.com \
--cc=masneyb@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@lists.linux.dev \
--cc=will@kernel.org \
--cc=zl020895@163.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
all inboxes | Powered by JetHome®