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:48:06 +0200 [thread overview]
Message-ID: <997b40d5-c96c-4587-a9c2-88ac0e561870@kernel.org> (raw)
In-Reply-To: <b35c8727-f6bf-4024-9e83-dfe12ac4400f@blaize.com>
On 05/05/2025 16:43, Nikolaos Pasaloukos wrote:
>>
>>> ---
>>>
>>> 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
>
> I am the platform maintainer for blaize but I haven't created an account
> yet on the kernel.org and according to Arnd it should be OK to submit the
> patches for inclusion (until I get an account) by sending them to the
> soc@lists.linux.dev.
>
> So, what would be preferable? To send only this patch with b4 or resend
> the v2 patchset which have been accepted and add the soc list?
soc@ is for applying patches, but your Cc list here suggest you send
something for review. These are two different processes, see soc
maintainer profile.
You need to handle the patches (collect them) after community review
*and then* you send these to soc@, without ccing again entire community.
See any other pull requests or patch-pull emails.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-05 14:48 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
2025-05-05 14:43 ` Nikolaos Pasaloukos
2025-05-05 14:48 ` 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=997b40d5-c96c-4587-a9c2-88ac0e561870@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