devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	"Rob Herring (Arm)" <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
	brcm80211@lists.linux.dev, asahi@lists.linux.dev,
	Hector Martin <marcan@marcan.st>
Subject: Re: [PATCH 1/2] dt-bindings: wireless: restore constraint for brcm,bcm4329-fmac compatible property
Date: Tue, 20 Aug 2024 13:50:47 +0200	[thread overview]
Message-ID: <8d74380c-0090-4209-963e-e7dde57c4235@kernel.org> (raw)
In-Reply-To: <7a5e37f0-4830-43f8-84c9-62b6614efaca@broadcom.com>

On 20/08/2024 13:43, Arend van Spriel wrote:
> On 8/20/2024 1:14 PM, Rob Herring (Arm) wrote:
>>
>> On Tue, 20 Aug 2024 12:12:15 +0200, Arend van Spriel wrote:
>>> When extending the bindings for Apple PCIe devices the compatible property
>>> specification was changed. However, it was changed such that for these
>>> devices it was no longer necessary to have "brcm,bcm4329-fmac" listed as
>>> string in the compatible list property as it was before that extension.
>>> This patch restores that constraint.
>>>
>>> Fixes: e2e37224e8b3 ("dt-bindings: net: bcm4329-fmac: Add Apple properties & chips")
>>> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>>> ---
>>>   .../net/wireless/brcm,bcm4329-fmac.yaml       | 19 ++++++++++---------
>>>   1 file changed, 10 insertions(+), 9 deletions(-)
>>>
>>
>> My bot found errors running 'make dt_binding_check' on your patch:
>>
>> yamllint warnings/errors:
>> ./Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml:48:5: [error] syntax error: expected <block end>, but found '-' (syntax)
>>
>> dtschema/dtc warnings/errors:
>> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml: ignoring, error parsing file
>> ./Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml:48:5: did not find expected key
>> Documentation/devicetree/bindings/mmc/mmc-controller.example.dtb: /example-0/mmc@1c12000/wifi@1: failed to match any schema with compatible: ['brcm,bcm4329-fmac']
>> make[2]: *** Deleting file 'Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.example.dts'
>> Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml:48:5: did not find expected key
>> make[2]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.example.dts] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1432: dt_binding_check] Error 2
>> make: *** [Makefile:224: __sub-make] Error 2
>>
>> doc reference errors (make refcheckdocs):
>>
>> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240820101216.355012-2-arend.vanspriel@broadcom.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.
> 
> Thanks, Rob
> 
> I will have to setup my environment for that. Will take a while to get 
> it all working.

It's just two commands:
pip install
or pix install if you use newer Ubuntu (no magic here, just like every
other Python package)

and then `make dt_bindings_check`, optionally with arguments. There is
no environment needed, you can do all this in the same place you build
and test kernel changes.

Best regards,
Krzysztof


  reply	other threads:[~2024-08-20 11:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 10:12 [PATCH 0/2] dt-bindings fixup for brcm,bcm4329-fmac.yaml Arend van Spriel
2024-08-20 10:12 ` [PATCH 1/2] dt-bindings: wireless: restore constraint for brcm,bcm4329-fmac compatible property Arend van Spriel
2024-08-20 11:14   ` Rob Herring (Arm)
2024-08-20 11:43     ` Arend van Spriel
2024-08-20 11:50       ` Krzysztof Kozlowski [this message]
2024-08-20 12:08         ` Arend van Spriel
2024-08-20 19:01         ` Arend van Spriel
2024-08-20 11:27   ` Krzysztof Kozlowski
2024-08-20 11:39     ` Krzysztof Kozlowski
2024-08-20 12:50       ` Arend van Spriel
2024-08-20 14:53         ` Arend Van Spriel
2024-08-20 15:37           ` Krzysztof Kozlowski
2024-08-20 15:36         ` Krzysztof Kozlowski
2024-08-20 15:50           ` Krzysztof Kozlowski
2024-08-20 19:29             ` Arend van Spriel
2024-08-21  6:46               ` Krzysztof Kozlowski
2024-08-22  0:26                 ` Julian Calaby
2024-08-22  6:29                   ` Arend Van Spriel
2024-08-20 10:12 ` [PATCH 2/2] arm64: boot: apple: fixup wifi device specification Arend van Spriel
2024-08-20 11:30   ` Krzysztof Kozlowski

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=8d74380c-0090-4209-963e-e7dde57c4235@kernel.org \
    --to=krzk@kernel.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=asahi@lists.linux.dev \
    --cc=brcm80211@lists.linux.dev \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcan@marcan.st \
    --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).