Skip to contentSkip to conversation

staging: wilc1000: remove label from examples in DT binding documentation

PATCH In review [email protected] 2 participants 3 messages Mar 25, 2020 – Mar 26, 2020 Staging

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 staging: wilc1000: remove label from examples in DT binding documentation

From: Ajay Singh <[email protected]>

Remove labels and not relevant property from DT binding documentation examples as suggested in [1].

1. https://patchwork.ozlabs.org/patch/1252837

---
 drivers/staging/wilc1000/microchip,wilc1000.yaml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/staging/wilc1000/microchip,wilc1000.yaml +2 -3
index bc6cc5d3f347..2c320eb2a8c4 100644
@@ -36,10 +36,9 @@ required:
 
 examples:
   - |
-    spi1: spi@fc018000 {
+    spi {
       #address-cells = <1>;
       #size-cells = <0>;
-      cs-gpios = <&pioB 21 0>;
       wifi@0 {
         compatible = "microchip,wilc1000";
         spi-max-frequency = <48000000>;
@@ -52,7 +51,7 @@ examples:
     };
 
   - |
-    mmc1: mmc@fc000000 {
+    mmc {
       #address-cells = <1>;
       #size-cells = <0>;
       pinctrl-names = "default";
Signature · 1 line
2.24.0
#1 lore raw
Quoted 6 lines · <[email protected]> writes:

From: Ajay Singh <[email protected]>

Remove labels and not relevant property from DT binding documentation examples as suggested in [1].

1. https://patchwork.ozlabs.org/patch/1252837

Just a nitpick but patchwork links are not that reliable in the long run. Instead using a lore link is better as the message id is visible directly from the URL.

Signature · 1 line
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
#2 lore raw

Hi Kalle,

Quoted 5 lines · Kalle Valo
Quoted 2 lines · <[email protected]> writes:

From: Ajay Singh <[email protected]>

Quoted 9 lines
Quoted 4 lines

Remove labels and not relevant property from DT binding documentation examples as suggested in [1].

1. https://patchwork.ozlabs.org/patch/1252837

Just a nitpick but patchwork links are not that reliable in the long run. Instead using a lore link is better as the message id is visible directly from the URL.

Sure. I will make use of lore link for future patches as this patch is already applied.

Regards,
Ajay