From: Rob Herring <robh@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Vidya Sagar" <vidyas@nvidia.com>, "Frank Li" <Frank.li@nxp.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
linux-pci@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: PCI: Remove obsolete .txt docs
Date: Mon, 7 Apr 2025 11:55:26 -0500 [thread overview]
Message-ID: <CAL_JsqL+i012pE2vrSWc-Tro58aAEZY4xe5n-LcoqN1RWES6RQ@mail.gmail.com> (raw)
In-Reply-To: <174380891321.749968.3085053836966154334.robh@kernel.org>
On Fri, Apr 4, 2025 at 6:21 PM Rob Herring (Arm) <robh@kernel.org> wrote:
>
>
> On Fri, 04 Apr 2025 17:15:57 -0500, Rob Herring (Arm) wrote:
> > The content in these files has been moved to the schemas in dtschema.
> > pci.txt is covered by pci-bus-common.yaml and pci-host-bridge.yaml.
> > pci-iommu.txt is covered by pci-iommu.yaml. pci-msi.txt is covered in
> > msi-map property in pci-host-bridge.yaml.
> >
> > Cc: Frank Li <Frank.li@nxp.com>
> > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> > ---
> > .../bindings/pci/nvidia,tegra194-pcie-ep.yaml | 2 +-
> > .../devicetree/bindings/pci/pci-iommu.txt | 171 --------------
> > .../devicetree/bindings/pci/pci-msi.txt | 220 ------------------
> > Documentation/devicetree/bindings/pci/pci.txt | 84 -------
> > 4 files changed, 1 insertion(+), 476 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/pci/pci-iommu.txt
> > delete mode 100644 Documentation/devicetree/bindings/pci/pci-msi.txt
> > delete mode 100644 Documentation/devicetree/bindings/pci/pci.txt
> >
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
>
>
> doc reference errors (make refcheckdocs):
> Warning: Documentation/devicetree/bindings/virtio/pci-iommu.yaml references a file that doesn't exist: Documentation/devicetree/bindings/pci/pci.txt
> Documentation/devicetree/bindings/virtio/pci-iommu.yaml: Documentation/devicetree/bindings/pci/pci.txt
I've fixed this with this[1] patch.
Rob
[1] https://lore.kernel.org/r/20250407165341.2934499-1-robh@kernel.org
next prev parent reply other threads:[~2025-04-07 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 22:15 [PATCH] dt-bindings: PCI: Remove obsolete .txt docs Rob Herring (Arm)
2025-04-04 23:21 ` Rob Herring (Arm)
2025-04-07 16:55 ` Rob Herring [this message]
2025-04-05 0:36 ` kernel test robot
2025-04-07 14:36 ` Frank Li
2025-04-20 4:15 ` Manivannan Sadhasivam
2025-04-22 17:18 ` Bjorn Helgaas
2025-04-23 13:02 ` Rob Herring
2025-04-23 22:36 ` Bjorn Helgaas
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=CAL_JsqL+i012pE2vrSWc-Tro58aAEZY4xe5n-LcoqN1RWES6RQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).