linux-kernel - Re: [PATCH v2 16/21] dt-bindings: spi: document support for SA8255p

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: <2f11f622-1a00-4558-bde9-4871cdc3d1a6@lunn.ch>
Date: Wed, 4 Sep 2024 18:58:38 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Nikunj Kela <quic_nkela@...cinc.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, andersson@...nel.org,
	konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
	conor+dt@...nel.org, rafael@...nel.org, viresh.kumar@...aro.org,
	herbert@...dor.apana.org.au, davem@...emloft.net,
	sudeep.holla@....com, andi.shyti@...nel.org, tglx@...utronix.de,
	will@...nel.org, robin.murphy@....com, joro@...tes.org,
	jassisinghbrar@...il.com, lee@...nel.org, linus.walleij@...aro.org,
	amitk@...nel.org, thara.gopinath@...il.com, broonie@...nel.org,
	cristian.marussi@....com, rui.zhang@...el.com, lukasz.luba@....com,
	wim@...ux-watchdog.org, linux@...ck-us.net,
	linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-crypto@...r.kernel.org, arm-scmi@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-i2c@...r.kernel.org,
	iommu@...ts.linux.dev, linux-gpio@...r.kernel.org,
	linux-serial@...r.kernel.org, linux-spi@...r.kernel.org,
	linux-watchdog@...r.kernel.org, kernel@...cinc.com,
	quic_psodagud@...cinc.com,
	Praveen Talari <quic_ptalari@...cinc.com>
Subject: Re: [PATCH v2 16/21] dt-bindings: spi: document support for SA8255p

> Sorry, didn't realize SPI uses different subject format than other
> subsystems. Will fix in v3. Thanks

Each subsystem is free to use its own form. e.g for netdev you will
want the prefix [PATCH net-next v42] net: stmmac: dwmac-qcom-ethqos:

This is another reason why you should be splitting these patches per
subsystem, and submitting both the DT bindings and the code changes as
a two patch patchset. You can then learn how each subsystem names its
patches.

Please pick one victim subsystem and work on the patches for just that
subsystem. Once you have them correct, you can use everything you
learned to fixup all your other patches, one by one.

	Andrew