From: Rob Herring <robh@kernel.org>
To: sashiko@lists.linux.dev
Cc: Matthew Leung <matthew.leung@oss.qualcomm.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: PCI: qcom: Document the Hawi PCIe Controller
Date: Wed, 13 May 2026 17:53:10 -0500 [thread overview]
Message-ID: <20260513225310.GA2251300-robh@kernel.org> (raw)
In-Reply-To: <20260508012135.76B34C2BCB2@smtp.kernel.org>
On Fri, May 08, 2026 at 01:21:34AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The compatible string and filename violate the established Qualcomm PCIe naming pattern.
> --
>
> commit 332996956780b2d8736ee1fcd6b38c1627f71689
> Author: Matthew Leung <matthew.leung@oss.qualcomm.com>
>
> dt-bindings: PCI: qcom: Document the Hawi PCIe Controller
>
> Add a dedicated schema for the PCIe controllers found on the Hawi
> platform.
>
> > diff --git a/Documentation/devicetree/bindings/pci/qcom,hawi-pcie.yaml b/Documentation/devicetree/bindings/pci/qcom,hawi-pcie.yaml
> > new file mode 100644
> > index 0000000000000..154bc88e59694
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pci/qcom,hawi-pcie.yaml
>
> This isn't a bug, but is there a reason this file isn't named
> qcom,pcie-hawi.yaml? The rest of the Qualcomm PCIe Root Complex bindings
> strictly follow the qcom,pcie-<soc> naming pattern, such as
> qcom,pcie-sc7280.yaml and qcom,pcie-sm8550.yaml.
Sashiko is wrong here.
>
> [ ... ]
>
> > +properties:
> > + compatible:
> > + const: qcom,hawi-pcie
>
> Should this compatible string also be changed to qcom,pcie-hawi to maintain
> consistency with the other Qualcomm Root Complex definitions across the
> subsystem?
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260508-hawi-pcie-v1-0-0c910906f7e5@oss.qualcomm.com?part=1
parent reply other threads:[~2026-05-13 22:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260508012135.76B34C2BCB2@smtp.kernel.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260513225310.GA2251300-robh@kernel.org \
--to=robh@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.leung@oss.qualcomm.com \
--cc=sashiko@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox