From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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, dd@embedd.com
Subject: Re: Support for airoha en7581 Soc
Date: Mon, 29 Jan 2024 16:25:59 +0100 [thread overview]
Message-ID: <f90a6034-b1ca-4245-a3cd-91d43152b780@collabora.com> (raw)
In-Reply-To: <ed322f44-6f7a-414d-a650-76c17c057b08@app.fastmail.com>
Il 29/01/24 16:22, Arnd Bergmann ha scritto:
> On Mon, Jan 29, 2024, at 16:08, Krzysztof Kozlowski wrote:
>> 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.
>
> I expect this to be picked up by the mediatek maintainers,
> same as what we did for the arch/arm/ port that was merged
> first.
Yes, we're doing that.
> While airoha is a separate company these days,
Not really... it's still a MediaTek subsidiary...
https://corp.mediatek.com/about/subsidiary-information
https://www.airoha.com/about
> I assume this is still closely related to mt7623, mt7683,
> and mt7622, just like en7523 was.
I assume the same. I'll add the airoha directory to the MAINTAINERS file
under ARM/Mediatek.
Cheers
Angelo
prev parent reply other threads:[~2024-01-29 15:26 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
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 [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=f90a6034-b1ca-4245-a3cd-91d43152b780@collabora.com \
--to=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=krzysztof.kozlowski@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