From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Felix Fietkau <nbd@nbd.name>,
devicetree@vger.kernel.org, John Crispin <john@phrozen.org>,
soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
dd@embedd.com
Subject: Re: Support for airoha en7581 Soc
Date: Mon, 29 Jan 2024 16:08:14 +0100 [thread overview]
Message-ID: <9e1ad877-f55c-4045-bb92-c30614d6c1ff@linaro.org> (raw)
In-Reply-To: <ZbeJ5okKQ66FXGxP@lore-desk>
On 29/01/2024 12:20, Lorenzo Bianconi wrote:
> Hi Matthias,
>
> I was wondering about the status of the following patches:
> https://lore.kernel.org/linux-arm-kernel/20231001122418.2688120-4-dd@embedd.com/T/#rbafabf4bf2473327f35ce7d79623f63838630537
>
> Do we need to respin them? Thx in advance.
I don't see anyone from SoC maintainers CCed on that patchset, so no one
will pick it up. Pinging makes sense if maintainers missed/ignored your
email. But if you do not send stuff to maintainers, you need to resend
to proper people, not ping.
Additionally, this is a new arch, but it seems to miss any maintainers
update.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-29 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 11:20 Support for airoha en7581 Soc Lorenzo Bianconi
2024-01-29 11:34 ` AngeloGioacchino Del Regno
2024-01-29 11:39 ` Conor Dooley
2024-01-29 11:41 ` AngeloGioacchino Del Regno
2024-01-29 13:19 ` Lorenzo Bianconi
2024-01-29 15:08 ` Krzysztof Kozlowski [this message]
2024-01-29 15:20 ` Lorenzo Bianconi
2024-01-29 15:25 ` Krzysztof Kozlowski
2024-01-29 15:22 ` Arnd Bergmann
2024-01-29 15:25 ` AngeloGioacchino Del Regno
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=9e1ad877-f55c-4045-bb92-c30614d6c1ff@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=dd@embedd.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=robh+dt@kernel.org \
--cc=soc@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 NNTP newsgroup(s).