linux-kernel - Re: [PATCH v6 2/8] i2c: muxes: add support for tsd,mule-i2c multiplexer

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]

Message-ID: <f6dfc6cc-365d-4f0a-9a4c-dc34cf4c5b7d@kernel.org>
Date: Mon, 12 Aug 2024 13:37:15 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
 Quentin Schulz <quentin.schulz@...rry.de>,
 Farouk Bouabid <farouk.bouabid@...rry.de>, Andi Shyti
 <andi.shyti@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Peter Rosin <peda@...ntia.se>,
 Jean Delvare <jdelvare@...e.com>, Guenter Roeck <linux@...ck-us.net>,
 Heiko Stuebner <heiko@...ech.de>, linux-i2c@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-hwmon@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH v6 2/8] i2c: muxes: add support for tsd,mule-i2c
 multiplexer

On 12/08/2024 12:06, Wolfram Sang wrote:
> 
>> Let's call it real ping, because we have warning in next due to this:
>>
>> Documentation/devicetree/bindings/hwmon/ti,amc6821.example.dtb: /example-1/i2c/fan@...i2c-mux: failed to match any schema with compatible: ['tsd,mule-i2c-mux']
> 
> So someone picked up patches before the dependencies were accepted? Bad
> idea.

Yep, but to be fair the patchset did not say anything about
dependencies. There is absolutely nothing in cover letter, nothing in
the patches, so I do not wonder that this mishap happened.

> 
>> Can anyone pick up the i2c pieces?
> 
> They need review first. We likely have an issue with resource
> availabilty here. It is that simple.
> 
>> And/or fix maintainers for your subsystem?
> 
> Have you looked at the entries? They look proper to me.

Depends whether you rely on being CC-ed here. Existing entries do not
include you, thus you are not cc-ed on maintainers. Peter Rosin is, but
it seems Peter does not apply patches. It could be intentional, but then
I understand that all pings should go to Peter?

Best regards,
Krzysztof