linux-kernel - Re: [PATCH v2] dt-bindings: interrupt-controller: riscv,cpu-intc: convert to dtschema

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]

Date: Sun, 19 May 2024 23:33:11 +0530
From: Kanak Shilledar <kanakshilledar@...il.com>
To: Conor Dooley <conor@...nel.org>
Cc: Kanak Shilledar <kanakshilledar111@...tonmail.com>, Thomas Gleixner <tglx@...utronix.de>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, 
	Conor Dooley <conor+dt@...nel.org>, Paul Walmsley <paul.walmsley@...ive.com>, 
	Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, 
	Samuel Holland <samuel.holland@...ive.com>, linux-kernel@...r.kernel.org, 
	devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v2] dt-bindings: interrupt-controller: riscv,cpu-intc:
 convert to dtschema

On Sun, May 19, 2024 at 7:29 PM Kanak Shilledar
<kanakshilledar@...il.com> wrote:
>
> > > On Sat, May 18, 2024 at 11:49:21AM +0530, Kanak Shilledar wrote:
> > > > +allOf:
> > > > +  - $ref: /schemas/riscv/cpus.yaml#/properties/interrupt-controller
> > > > +
> > > > +properties:
> > > > +  compatible:
> > > > +    $ref: /schemas/riscv/cpus.yaml#/properties/interrupt-controller/properties/compatible
> > >
> > >
> > > Unfortunately, this is still not what I was asking you to do :/
> > > I said to make the copy in cpus.yaml a reference to this binding.
> >
> > Sorry for misinterpreting the comments. I will fix it right away.
> > > Cheers,
> > > Conor.
>
> I have done the changes and created two commits for the respective
> files cpus.yaml and riscv,cpu-intc.yaml.
> I am having v3 for the riscv,cpu-intc.yaml but cpus.yaml will be on
> v1. So shall I mail them separately or
> merge both the commits in a single one?
>
> Thanks and Regards,
> Kanak Shilledar

I referred to the documentation and created a patchset with a cover
letter to have both the commits separated
in different patches.
https://lore.kernel.org/linux-devicetree/20240519175906.138410-1-kanakshilledar111@protonmail.com/T/#t

Thanks and Regards,
Kanak Shilledar