linux-kernel - Re: [PATCH RESEND] arm: marvell: Fix maxium->maxim typo for brownstone dts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 25 Aug 2023 23:06:29 +0200
From:   Duje Mihanović <duje.mihanovic@...le.hr>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Lubomir Rintel <lkundrak@...sk>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] arm: marvell: Fix maxium->maxim typo for brownstone dts

On Tuesday, August 22, 2023 1:43:08 AM CEST Andrew Lunn wrote:
> Maybe a dumb question. Does I2C core still ignore the vendor part? Its
> a long time since i did anything with i2c, but i thought for
> historical reasons it ignore the vendor?
>
> If this is still true, then yes, this is just a spelling
> error. However, if the vendor is being used to match device to driver,
> this is more than a spelling issue, and should be directed to stable.

I have just tested this by changing the MUIC compatible on my (not yet 
upstreamed) samsung,coreprimevelte board from "siliconmitus,sm5504-muic" to 
"siliconnitus,sm5504-muic". With this change USB no longer works, presumably 
because USB probing gets deferred forever since this MUIC referenced in USB's 
extcon never gets probed.

I assume this PMIC would behave identically and thus this should go to stable. 
Would this be done by sending a v2 with the Cc: tag added?

Regards,
Duje