From: Arend Van Spriel <arend.vanspriel@broadcom.com> To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>, kvalo@codeaurora.org, robh+dt@kernel.org, mark.rutland@arm.com, devicetree@vger.kernel.org Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH 1/1] dt-binding: net: wireless: fix node name in the BCM43xx example Date: Tue, 16 May 2017 00:05:30 +0200 [thread overview] Message-ID: <8155d0f1-aed3-fc47-4524-635067f9ee7b@broadcom.com> (raw) In-Reply-To: <20170515201356.26384-2-martin.blumenstingl@googlemail.com> On 15-5-2017 22:13, Martin Blumenstingl wrote: > The example in the BCM43xx documentation uses "brcmf" as node name. > However, wireless devices should be named "wifi" instead. Fix this to Hi Martin, Since when is that a rule. I never got the memo and the DTC did not ever complain to me about the naming. That being said I do not really care and I suppose it is for the sake of consistency only. > make sure that .dts authors can simply use the documentation as > reference (or simply copy the node from the documentation and then > adjust only the board specific bits). Please feel free to add my... Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com> > Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> > --- > Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > index 5dbf169cd81c..590f622188de 100644 > --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > @@ -31,7 +31,7 @@ mmc3: mmc@01c12000 { > non-removable; > status = "okay"; > > - brcmf: bcrmf@1 { > + brcmf: wifi@1 { > reg = <1>; > compatible = "brcm,bcm4329-fmac"; > interrupt-parent = <&pio>; >
WARNING: multiple messages have this Message-ID (diff)
From: Arend Van Spriel <arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> To: Martin Blumenstingl <martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>, kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, mark.rutland-5wv7dgnIgG8@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH 1/1] dt-binding: net: wireless: fix node name in the BCM43xx example Date: Tue, 16 May 2017 00:05:30 +0200 [thread overview] Message-ID: <8155d0f1-aed3-fc47-4524-635067f9ee7b@broadcom.com> (raw) In-Reply-To: <20170515201356.26384-2-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> On 15-5-2017 22:13, Martin Blumenstingl wrote: > The example in the BCM43xx documentation uses "brcmf" as node name. > However, wireless devices should be named "wifi" instead. Fix this to Hi Martin, Since when is that a rule. I never got the memo and the DTC did not ever complain to me about the naming. That being said I do not really care and I suppose it is for the sake of consistency only. > make sure that .dts authors can simply use the documentation as > reference (or simply copy the node from the documentation and then > adjust only the board specific bits). Please feel free to add my... Acked-by: Arend van Spriel <arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> > Signed-off-by: Martin Blumenstingl <martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> > --- > Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > index 5dbf169cd81c..590f622188de 100644 > --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt > @@ -31,7 +31,7 @@ mmc3: mmc@01c12000 { > non-removable; > status = "okay"; > > - brcmf: bcrmf@1 { > + brcmf: wifi@1 { > reg = <1>; > compatible = "brcm,bcm4329-fmac"; > interrupt-parent = <&pio>; > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-15 22:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-15 20:13 [PATCH 0/1] fix node name in the brcm,bcm43xx-fmac.txt example Martin Blumenstingl 2017-05-15 20:13 ` Martin Blumenstingl 2017-05-15 20:13 ` [PATCH 1/1] dt-binding: net: wireless: fix node name in the BCM43xx example Martin Blumenstingl 2017-05-15 20:13 ` Martin Blumenstingl 2017-05-15 22:05 ` Arend Van Spriel [this message] 2017-05-15 22:05 ` Arend Van Spriel 2017-05-16 19:56 ` Martin Blumenstingl 2017-05-16 19:56 ` Martin Blumenstingl 2017-05-21 14:19 ` Andreas Färber 2017-05-21 14:19 ` Andreas Färber 2017-05-22 9:37 ` Arend van Spriel 2017-05-22 9:37 ` Arend van Spriel 2017-05-19 1:56 ` Rob Herring 2017-05-21 14:54 ` Andreas Färber 2017-05-21 14:54 ` Andreas Färber 2017-05-21 14:54 ` Andreas Färber
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=8155d0f1-aed3-fc47-4524-635067f9ee7b@broadcom.com \ --to=arend.vanspriel@broadcom.com \ --cc=devicetree@vger.kernel.org \ --cc=kvalo@codeaurora.org \ --cc=linux-wireless@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=martin.blumenstingl@googlemail.com \ --cc=netdev@vger.kernel.org \ --cc=robh+dt@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.