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: <a7ea63b0-f787-49f2-8e31-d3849b6b0518@kernel.org>
Date: Fri, 6 Feb 2026 08:06:10 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Gary Yang <gary.yang@...tech.com>
Cc: "robh@...nel.org" <robh@...nel.org>,
 "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>,
 "p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
 Peter Chen <peter.chen@...tech.com>,
 "unicorn_wang@...look.com" <unicorn_wang@...look.com>,
 "inochiama@...il.com" <inochiama@...il.com>,
 "alchark@...il.com" <alchark@...il.com>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 cix-kernel-upstream <cix-kernel-upstream@...tech.com>
Subject: Re: 回复: 回复: [PATCH v7 1/3] dt-bindings: soc: cix: document the simple-mfd syscon on Sky1 SoC

On 06/02/2026 06:42, Gary Yang wrote:
>>>
>>> This yaml comes from microchip,mpfs-mss-top-sysreg.yaml as conor's
>> suggestions on V3.
>>> More info:
>>> https://patchwork.kernel.org/project/linux-arm-kernel/patch/2025112406
>>> 3235.952136-2-gary.yang@...tech.com/
>>
>> Please point to a specific message, not entire thread of 8 untrimmed replies.
>>
> 
> Please pay attention to these below:
> 
>> Three, In corresponding driver files, we can get the regmap pointers via syscon API.
>> All right? By the way, How should we describe syscon in yaml file? Are there some files used to refer?
> 
> microchip,mpfs-mss-top-sysreg.yaml is one I wrote recently. Going to the

I do not understand why you are referring to this example. You did
nothing like that.

If you followed that example, it would be obviously fine because it is
correct. You did not follow that one - you have no children here - thus
you just proven that you received review which you just ignored. Sorry,
that's waste of our time. If you go that way, don't be surprised we are
grumpy. How many examples we need to give you which you can ignore...


Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ