From: Rob Herring <robh@kernel.org>
To: Saurabh Sengar <ssengar@linux.microsoft.com>
Cc: tglx@linutronix.de, kys@microsoft.com,
linux-hyperv@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
wei.liu@kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mikelley@microsoft.com,
virtualization@lists.linux-foundation.org,
haiyangz@microsoft.com, decui@microsoft.com,
daniel.lezcano@linaro.org, ssengar@microsoft.com
Subject: Re: [PATCH v2 4/6] dt-bindings: hypervisor: Rename virtio to hypervisor
Date: Tue, 31 Jan 2023 13:57:36 -0600 [thread overview]
Message-ID: <167519443459.1836211.1945655170442861713.robh@kernel.org> (raw)
In-Reply-To: <1675188609-20913-5-git-send-email-ssengar@linux.microsoft.com>
On Tue, 31 Jan 2023 10:10:07 -0800, Saurabh Sengar wrote:
> Rename virtio folder to more generic hypervisor, so that this can
> accommodate more devices of similar type.
>
> Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> ---
> .../devicetree/bindings/{virtio => hypervisor}/mmio.yaml | 2 +-
> .../devicetree/bindings/{virtio => hypervisor}/pci-iommu.yaml | 2 +-
> .../bindings/{virtio => hypervisor}/virtio-device.yaml | 2 +-
> MAINTAINERS | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
> rename Documentation/devicetree/bindings/{virtio => hypervisor}/mmio.yaml (95%)
> rename Documentation/devicetree/bindings/{virtio => hypervisor}/pci-iommu.yaml (98%)
> rename Documentation/devicetree/bindings/{virtio => hypervisor}/virtio-device.yaml (93%)
>
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:
dtschema/dtc warnings/errors:
./Documentation/devicetree/bindings/i2c/i2c-virtio.yaml: Unable to find schema file matching $id: http://devicetree.org/schemas/virtio/virtio-device.yaml
./Documentation/devicetree/bindings/gpio/gpio-virtio.yaml: Unable to find schema file matching $id: http://devicetree.org/schemas/virtio/virtio-device.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/i2c-virtio.example.dtb: i2c: False schema does not allow {'compatible': ['virtio,device22'], '#address-cells': [[1]], '#size-cells': [[0]], 'light-sensor@20': {'compatible': ['dynaimage,al3320a'], 'reg': [[32]]}, '$nodename': ['i2c']}
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/i2c-virtio.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/gpio/gpio-virtio.example.dtb: gpio: False schema does not allow {'compatible': ['virtio,device29'], 'gpio-controller': True, '#gpio-cells': [[2]], 'interrupt-controller': True, '#interrupt-cells': [[2]], '$nodename': ['gpio']}
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/gpio/gpio-virtio.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/hypervisor/virtio-device.example.dtb: i2c: False schema does not allow {'compatible': ['virtio,device22'], '$nodename': ['i2c']}
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/i2c-virtio.yaml
doc reference errors (make refcheckdocs):
MAINTAINERS: Documentation/devicetree/bindings/virtio/
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/1675188609-20913-5-git-send-email-ssengar@linux.microsoft.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
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 after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2023-01-31 19:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:10 [PATCH v2 0/6] Device tree support for Hyper-V VMBus driver Saurabh Sengar
2023-01-31 18:10 ` [PATCH v2 1/6] drivers/clocksource/hyper-v: non ACPI support in hyperv clock Saurabh Sengar
2023-01-31 18:10 ` [PATCH v2 2/6] Drivers: hv: allow non ACPI compilation for hv_is_hibernation_supported Saurabh Sengar
2023-02-01 17:47 ` Michael Kelley (LINUX)
2023-02-02 14:48 ` Saurabh Singh Sengar
2023-02-02 15:33 ` Michael Kelley (LINUX)
2023-01-31 18:10 ` [PATCH v2 3/6] Drivers: hv: vmbus: Convert acpi_device to platform_device Saurabh Sengar
2023-02-01 18:32 ` Michael Kelley (LINUX)
2023-02-02 15:27 ` Saurabh Singh Sengar
2023-02-03 5:32 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 4/6] dt-bindings: hypervisor: Rename virtio to hypervisor Saurabh Sengar
2023-01-31 19:57 ` Rob Herring [this message]
2023-02-01 5:36 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 5/6] dt-bindings: hypervisor: Add dt-bindings for VMBus Saurabh Sengar
2023-01-31 18:51 ` Krzysztof Kozlowski
2023-02-01 1:39 ` Saurabh Singh Sengar
2023-01-31 18:54 ` Krzysztof Kozlowski
2023-02-01 1:57 ` Saurabh Singh Sengar
2023-02-01 7:23 ` Krzysztof Kozlowski
2023-02-01 8:05 ` Saurabh Singh Sengar
2023-01-31 18:10 ` [PATCH v2 6/6] Driver: VMBus: Add device tree support Saurabh Sengar
2023-01-31 20:12 ` Rob Herring
2023-02-01 16:51 ` Saurabh Singh Sengar
2023-02-01 17:46 ` Rob Herring
2023-02-01 18:31 ` Saurabh Singh Sengar
2023-02-03 17:36 ` Saurabh Singh Sengar
2023-02-07 17:38 ` Rob Herring
2023-02-08 2:30 ` Saurabh Singh Sengar
2023-01-31 20:27 ` [PATCH v2 0/6] Device tree support for Hyper-V VMBus driver Rob Herring
2023-02-01 2:04 ` Saurabh Singh Sengar
2023-02-01 14:51 ` Rob Herring
2023-02-01 16:34 ` Saurabh Singh Sengar
2023-02-01 17:15 ` Krzysztof Kozlowski
2023-02-06 17:40 ` Saurabh Singh Sengar
2023-02-07 17:53 ` Rob Herring
2023-02-08 2:44 ` Saurabh Singh Sengar
2023-02-07 18:37 ` Sudeep Holla
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=167519443459.1836211.1945655170442861713.robh@kernel.org \
--to=robh@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=robh+dt@kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.liu@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
all inboxes | Powered by JetHome®