From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Niko Pasaloukos <nikolaos.pasaloukos@blaize.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"olof@lixom.net" <olof@lixom.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"sboyd@kernel.org" <sboyd@kernel.org>
Subject: Re: [PATCH v2 0/7] Add support for Blaize BLZP1600 SoC
Date: Wed, 24 Apr 2024 16:12:13 +0200 [thread overview]
Message-ID: <a2af498e-5db7-4362-b3b8-486c2c38b8b2@linaro.org> (raw)
In-Reply-To: <20240424133032.19056-1-nikolaos.pasaloukos@blaize.com>
On 24/04/2024 15:31, Niko Pasaloukos wrote:
> Adds basic support for the Blaize BLZP1600 SoC.
> This SoC contains two cores of Cortex-A53 CPUs, one Blaize
> Graph Streaming Processor (GSP) and several other IPs.
>
> V2 changes:
> * Update SoBs.
> * `make dtbs_check` has no warnings.
> * Fix dts names and removed dead code.
> * DTS is separated from anything else.
Your threading is totally broken.
I recommend using b4, if sending patches is tricky. b4 nicely solves
such (and many more) issues.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-04-24 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 13:31 [PATCH v2 0/7] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-04-24 14:12 ` Krzysztof Kozlowski [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=a2af498e-5db7-4362-b3b8-486c2c38b8b2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=olof@lixom.net \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).