From: Kalle Valo <kvalo@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Felix Fietkau" <nbd@nbd.name>,
"Lorenzo Bianconi" <lorenzo@kernel.org>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Shayne Chen" <shayne.chen@mediatek.com>,
"Sean Wang" <sean.wang@mediatek.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"de Goede" <hdegoede@redhat.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, ath11k@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: net: wireless: minor whitespace and name cleanups
Date: Thu, 19 Jan 2023 07:13:52 +0200 [thread overview]
Message-ID: <87bkmv85tb.fsf@kernel.org> (raw)
In-Reply-To: <20230118175413.360153-1-krzysztof.kozlowski@linaro.org> (Krzysztof Kozlowski's message of "Wed, 18 Jan 2023 18:54:13 +0100")
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:
> Minor cleanups:
> - Drop redundant blank lines,
> - Correct indentaion in examples,
> - Correct node names in examples to drop underscore and use generic
> name.
>
> No functional impact except adjusting to preferred coding style.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/net/wireless/esp,esp8089.yaml | 20 +++---
> .../bindings/net/wireless/ieee80211.yaml | 1 -
> .../bindings/net/wireless/mediatek,mt76.yaml | 1 -
> .../bindings/net/wireless/qcom,ath11k.yaml | 11 ++-
> .../bindings/net/wireless/silabs,wfx.yaml | 1 -
> .../bindings/net/wireless/ti,wlcore.yaml | 70 +++++++++----------
> 6 files changed, 50 insertions(+), 54 deletions(-)
Thanks for the cleanup. Would you like to me to take this to
wireless-next or do you have other plans?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-01-20 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:54 [PATCH] dt-bindings: net: wireless: minor whitespace and name cleanups Krzysztof Kozlowski
2023-01-19 5:13 ` Kalle Valo [this message]
2023-01-19 7:32 ` Krzysztof Kozlowski
2023-01-23 20:18 ` Rob Herring
2023-02-13 16:50 ` Kalle Valo
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=87bkmv85tb.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hdegoede@redhat.com \
--cc=jerome.pouiller@silabs.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=tony@atomide.com \
/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).