From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Paul Cercueil <paul@crapouillou.net>,
Kalle Valo <kvalo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arend van Spriel <arend@broadcom.com>
Cc: list@opendingux.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: bcm4329-fmac: Add ingenic,iw8103-fmac compatible string
Date: Mon, 19 Dec 2022 13:00:57 +0100 [thread overview]
Message-ID: <8485b70f-4120-192c-3f7e-6b4c8ac2ec33@broadcom.com> (raw)
In-Reply-To: <036c3985-0dcc-c860-4db2-22f0dd4550dc@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On 12/14/2022 5:53 PM, Krzysztof Kozlowski wrote:
> On 14/12/2022 16:59, Paul Cercueil wrote:
>> The MIPS CI20 board has a Ingenic IW8103 chip, which is supposedly just
>> a rebranded Broadcom BCM4330.
>>
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
My guess is that Ingenic is not really a chip manufacturer, but this is
actually a wifi module using BCM4330 as wifi chip. Personally, I would
not add a compatible string for that and the commit message does not
offer any arguments for having this.
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
prev parent reply other threads:[~2022-12-19 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 15:59 [PATCH] dt-bindings: bcm4329-fmac: Add ingenic,iw8103-fmac compatible string Paul Cercueil
2022-12-14 16:53 ` Krzysztof Kozlowski
2022-12-19 12:00 ` Arend van Spriel [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=8485b70f-4120-192c-3f7e-6b4c8ac2ec33@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=list@opendingux.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@crapouillou.net \
--cc=robh+dt@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