linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gogada, Bharat Kumar" <bharat.kumar.gogada@amd.com>
To: Rob Herring <robh@kernel.org>,
	Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"michals@xilinx.com" <michals@xilinx.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [PATCH v5 1/2] dt-bindings: PCI: xilinx-cpm: Add Versal CPM5 Root Port
Date: Tue, 21 Jun 2022 11:34:19 +0000	[thread overview]
Message-ID: <MW3PR12MB4411E3A3A8BD74191AC7754EBAB39@MW3PR12MB4411.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1655659215.212817.1922479.nullmailer@robh.at.kernel.org>

> On Sat, 18 Jun 2022 08:14:58 +0530, Bharat Kumar Gogada wrote:
> > Xilinx Versal Premium series has CPM5 block which supports Root Port
> > functionality at Gen5 speed.
> >
> > Add support for YAML schemas documentation for Versal CPM5 Root Port
> driver.
> >
> > Signed-off-by: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
> > ---
> >  .../bindings/pci/xilinx-versal-cpm.yaml       | 38 ++++++++++++++++++-
> >  1 file changed, 37 insertions(+), 1 deletion(-)
> >
> 
> My bot found errors running 'make DT_CHECKER_FLAGS=-m
> dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
> 
> yamllint warnings/errors:
> ./Documentation/devicetree/bindings/pci/xilinx-versal-cpm.yaml:17:7:
> [warning] wrong indentation: expected 4 but found 6 (indentation)
> 
> dtschema/dtc warnings/errors:
> 
> doc reference errors (make refcheckdocs):
> 
> See https://patchwork.ozlabs.org/patch/
> 
> This check can fail if there are any dependencies. The base for a patch series
> is generally the most recent rc1.
> 
> If you already ran 'make dt_binding_check' and didn't see the above error(s),
> then make sure 'yamllint' is installed and dt-schema is up to
> date:
> 
> pip3 install dtschema --upgrade
> 
> Please check and re-submit.
Hi Rob, will check and re submit.

Regards,
Bharat

  reply	other threads:[~2022-06-21 11:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  2:44 [PATCH v5 0/2] Add support for Xilinx Versal CPM5 Root Port Bharat Kumar Gogada
2022-06-18  2:44 ` [PATCH v5 1/2] dt-bindings: PCI: xilinx-cpm: Add " Bharat Kumar Gogada
2022-06-19 17:20   ` Rob Herring
2022-06-21 11:34     ` Gogada, Bharat Kumar [this message]
2022-06-18  2:44 ` [PATCH v5 2/2] PCI: xilinx-cpm: Add support for " Bharat Kumar Gogada
  -- strict thread matches above, loose matches on Subject: below --
2022-06-21 11:36 [PATCH v5 0/2] Add support for Xilinx " Bharat Kumar Gogada
2022-06-21 11:36 ` [PATCH v5 1/2] dt-bindings: PCI: xilinx-cpm: Add " Bharat Kumar Gogada
2022-06-28 19:37   ` Rob Herring
2022-06-16 12:44 [PATCH v5 0/2] Add support for Xilinx " Bharat Kumar Gogada
2022-06-16 12:44 ` [PATCH v5 1/2] dt-bindings: PCI: xilinx-cpm: Add " Bharat Kumar Gogada
2022-06-18  2:38   ` Gogada, Bharat Kumar

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=MW3PR12MB4411E3A3A8BD74191AC7754EBAB39@MW3PR12MB4411.namprd12.prod.outlook.com \
    --to=bharat.kumar.gogada@amd.com \
    --cc=bharat.kumar.gogada@xilinx.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=michals@xilinx.com \
    --cc=robh@kernel.org \
    /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).