linux-kernel - Re: [PATCH v3] dt-bindings: i2c: i2c-wmt: Convert to YAML

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] [day] [month] [year] [list]

Message-ID: <c36emmsymieo5npmv5omd37yumkmmai3hozkypc5p4u3apensh@yb53oh3mv6qu>
Date: Thu, 8 May 2025 14:42:08 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Alexey Charkov <alchark@...il.com>, Rob Herring <robh@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	linux-arm-kernel@...ts.infradead.org, linux-i2c@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v3] dt-bindings: i2c: i2c-wmt: Convert to YAML

On Thu, May 08, 2025 at 12:33:21PM +0200, Krzysztof Kozlowski wrote:
> On 08/05/2025 12:31, Andi Shyti wrote:
> >> index 16037aaa770fc35efb45fc26555afaa5102e2640..4d18afdaf12bf6a5956793814f8db39b34074a12 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -3464,7 +3464,7 @@ M:	Krzysztof Kozlowski <krzk@...nel.org>
> >>  L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
> >>  S:	Odd Fixes
> >>  F:	Documentation/devicetree/bindings/hwinfo/via,vt8500-scc-id.yaml
> >> -F:	Documentation/devicetree/bindings/i2c/i2c-wmt.txt
> >> +F:	Documentation/devicetree/bindings/i2c/wm,wm8505-i2c.yaml
> > 
> > this has caused some conflict. You are based on -next but i2c
> > hasn't received some of these changes, yet.
> > 
> > Anyway, I fixed the conflict and merged to i2c/i2c-host. Let's
> > see how it goes, but I believe we will receive some complaints in
> > the next days.
> Yes, few trees will have similar conflicts here. Expect them also when
> you send your pull to Linus. Conflicts should be trivial, though.

Thanks for confirming this, Krzysztof!

Andi