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: Thu, 1 Feb 2024 16:36:15 -0600
From: Rob Herring <robh@...nel.org>
To: Dharma.B@...rochip.com
Cc: sam@...nborg.org, bbrezillon@...nel.org,
	maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
	tzimmermann@...e.de, airlied@...il.com, daniel@...ll.ch,
	krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
	Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com,
	claudiu.beznea@...on.dev, dri-devel@...ts.freedesktop.org,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, lee@...nel.org,
	thierry.reding@...il.com, u.kleine-koenig@...gutronix.de,
	linux-pwm@...r.kernel.org, Hari.PrasathGE@...rochip.com,
	Manikandan.M@...rochip.com
Subject: Re: [linux][PATCH v5 0/3] Convert Microchip's HLCDC Text based DT
 bindings to JSON schema

On Thu, Feb 01, 2024 at 03:38:37AM +0000, Dharma.B@...rochip.com wrote:
> Hi Rob,
> 
> On 31/01/24 9:05 am, Dharma B - I70843 wrote:
> > Converted the text bindings to YAML and validated them individually using following commands
> > 
> > $ make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/
> > $ make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/
> > 
> > changelogs are available in respective patches.
> > 
> > As Sam suggested I'm sending the PWM binding as it is in this patch series, clean up patch
> > will be sent as separate patch.
> > 
> 
> I would want to know if I can have the examples in display and pwm 
> bindings separately or if I have to delete them from both and have a 
> single, comprehensive example in mfd binding. I'm a little puzzled about 
> this.

The strong preference is 1 complete example in the MFD binding. That 
avoids 2 copies of the same thing, issues with incomplete examples, 
and temporary warnings bisecting the series.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ