From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Niko Pasaloukos <nikolaos.pasaloukos@blaize.com>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"olof@lixom.net" <olof@lixom.net>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"hvilleneuve@dimonoff.com" <hvilleneuve@dimonoff.com>,
"andre.przywara@arm.com" <andre.przywara@arm.com>,
"rafal@milecki.pl" <rafal@milecki.pl>,
"andersson@kernel.org" <andersson@kernel.org>,
"konrad.dybcio@linaro.org" <konrad.dybcio@linaro.org>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"nm@ti.com" <nm@ti.com>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"nfraprado@collabora.com" <nfraprado@collabora.com>,
"johan+linaro@kernel.org" <johan+linaro@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/6] arm64: Add Blaize BLZP1600 SoC family
Date: Fri, 8 Nov 2024 11:57:03 +0100 [thread overview]
Message-ID: <3ed7ac41-1f07-4711-a816-7dcf06f4cda4@linaro.org> (raw)
In-Reply-To: <20241108103120.9955-4-nikolaos.pasaloukos@blaize.com>
On 08/11/2024 11:31, Niko Pasaloukos wrote:
> Add ARCH_BLAIZE_BLZP1600 SoC family to the arm64 architecture.
>
> Resolves: PESW-2604
> Checkpatch: ignore
NAK.
Please run scripts/checkpatch.pl and fix reported warnings. Then please
run `scripts/checkpatch.pl --strict` and (probably) fix more warnings.
Some warnings can be ignored, especially from --strict run, but the code
here looks like it needs a fix. Feel free to get in touch if the warning
is not clear.
>
> Reviewed-by: James Cowgill <james.cowgill@blaize.com>
> Reviewed-by: Matt Redfearn <matt.redfearn@blaize.com>
> Reviewed-by: Neil Jones <neil.jones@blaize.com>
Are these real reviews?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-08 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 10:31 [PATCH v4 0/6] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-08 10:31 ` [PATCH v4 1/6] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2024-11-08 10:54 ` Krzysztof Kozlowski
2024-11-08 14:18 ` Nikolaos Pasaloukos
2024-11-08 12:06 ` Krzysztof Kozlowski
2024-11-08 10:31 ` [PATCH v4 2/6] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-08 10:56 ` Krzysztof Kozlowski
2024-11-08 10:31 ` [PATCH v4 3/6] arm64: Add Blaize BLZP1600 SoC family Niko Pasaloukos
2024-11-08 10:57 ` Krzysztof Kozlowski [this message]
2024-11-08 10:31 ` [PATCH v4 4/6] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2024-11-08 11:36 ` Arnd Bergmann
2024-11-08 10:31 ` [PATCH v4 5/6] arm64: defconfig: Enable ARCH_BLAIZE_BLZP1600 Niko Pasaloukos
2024-11-08 10:59 ` Krzysztof Kozlowski
2024-11-08 10:31 ` [PATCH v4 6/6] MAINTAINER: Add entry for Blaize SoC Niko Pasaloukos
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=3ed7ac41-1f07-4711-a816-7dcf06f4cda4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=andre.przywara@arm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hvilleneuve@dimonoff.com \
--cc=james.cowgill@blaize.com \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.armstrong@linaro.org \
--cc=neil.jones@blaize.com \
--cc=nfraprado@collabora.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--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®