linux-kernel - Re: [PATCH RFC 0/7] PCI: enable Power and configure the QPS615 PCIe switch

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240701175149.GA10638@bhelgaas>
Date: Mon, 1 Jul 2024 12:51:49 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Krishna chaitanya chundru <quic_krichai@...cinc.com>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Krzysztof Wilczyński <kw@...ux.com>,
	Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Bjorn Andersson <andersson@...nel.org>,
	Konrad Dybcio <konrad.dybcio@...aro.org>,
	Jingoo Han <jingoohan1@...il.com>, quic_vbadigan@...cinc.com,
	quic_skananth@...cinc.com, quic_nitegupt@...cinc.com,
	linux-arm-msm@...r.kernel.org, linux-pci@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 0/7] PCI: enable Power and configure the QPS615 PCIe
 switch

On Wed, Jun 26, 2024 at 06:07:48PM +0530, Krishna chaitanya chundru wrote:
>       dt: bindings: add qcom,qps615.yaml
>       arm64: dts: qcom: qcs6490-rb3gen2: Add qps615 node
>       pci: Change the parent of the platform devices for child OF nodes
>       pci: Add new start_link() & stop_link function ops
>       pci: dwc: Add support for new pci function op
>       pci: qcom: Add support for start_link() & stop_link()
>       pci: pwrctl: Add power control driver for qps615

Run "git log --oneline" on these files and match the style.
"PCI: Change ...", "PCI: qcom:", "PCI/pwrctl", etc.

The colon vs slash convention isn't obvious, but this is how we've
applied it in the past:

For PCI core features like MSI, PM, ASPM, AER, DOE, etc:

  PCI/<feature>: <Text>

For PCI drivers outside the PCI core, like dwc, qcom, imx6, etc:

  PCI: <driver name>: <Text>