From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
"soc@lists.linux.dev" <soc@lists.linux.dev>
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: arm64: dts: blaize-blzp1600: Enable GPIO support
Date: Mon, 5 May 2025 16:17:53 +0200 [thread overview]
Message-ID: <32d9f0c5-5648-4cc2-9db6-f5165d20d20c@kernel.org> (raw)
In-Reply-To: <20250327-kernel-upstreaming-add_gpio_support-v2-3-2c45a1acdc0c@blaize.com>
On 05/05/2025 16:14, Nikolaos Pasaloukos wrote:
> Blaize BLZP1600 uses the custom silicon provided from
>
> VeriSilicon to add GPIO support.
>
> This interface is used to control signals on many other
>
> peripherals, such as Ethernet, USB, SD and eMMC.
>
>
> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
Entire patch is corrupted by your mail server. Please switch to b4 relay
if your mail server is not capable of sending emails (like Microsoft
Outlook).
Please use standard email subjects, so with the PATCH keyword in the
title. `git format-patch -vX` helps here to create proper versioned
patches. Another useful tool is b4. Skipping the PATCH keyword makes
filtering of emails more difficult thus making the review process less
convenient.
>
> ---
>
> I am re-sending the patch to include the soc list. The original patchset
>
> has already been applied but not this patch.
>
> Arnd, could you please apply or do I need someone to review?
Platform maintainers are responsible for the patches for their platform.
Any reason why this is not working for blaize?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-05 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250327-kernel-upstreaming-add_gpio_support-v2-0-2c45a1acdc0c@blaize.com>
2025-05-05 14:14 ` arm64: dts: blaize-blzp1600: Enable GPIO support Nikolaos Pasaloukos
2025-05-05 14:17 ` Krzysztof Kozlowski [this message]
2025-05-05 14:43 ` Nikolaos Pasaloukos
2025-05-05 14:48 ` Krzysztof Kozlowski
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=32d9f0c5-5648-4cc2-9db6-f5165d20d20c@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=robh@kernel.org \
--cc=soc@lists.linux.dev \
/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