linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Vinod Koul <vkoul@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Min Guo <min.guo@mediatek.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH next v3 01/16] dt-bindings: usb: fix yamllint check warning
Date: Tue, 9 Feb 2021 14:44:12 -0600	[thread overview]
Message-ID: <20210209204412.GA139333@robh.at.kernel.org> (raw)
In-Reply-To: <20210201070016.41721-1-chunfeng.yun@mediatek.com>

On Mon, Feb 01, 2021 at 03:00:01PM +0800, Chunfeng Yun wrote:
> Fix warning: "missing starting space in comment"
> 

I'm not seeing this warning in linux-next. It may already be fixed.

> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> v2~v3: no changes
> ---
>  Documentation/devicetree/bindings/usb/usb-device.yaml | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/usb/usb-device.yaml b/Documentation/devicetree/bindings/usb/usb-device.yaml
> index 7bb25a45427d..23e76cfb2066 100644
> --- a/Documentation/devicetree/bindings/usb/usb-device.yaml
> +++ b/Documentation/devicetree/bindings/usb/usb-device.yaml
> @@ -82,9 +82,9 @@ required:
>  additionalProperties: true
>  
>  examples:
> -  #hub connected to port 1
> -  #device connected to port 2
> -  #device connected to port 3
> +  # hub connected to port 1
> +  # device connected to port 2
> +  # device connected to port 3
>    #    interface 0 of configuration 1
>    #    interface 0 of configuration 2
>    - |
> -- 
> 2.18.0

      parent reply	other threads:[~2021-02-09 21:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  7:00 [PATCH next v3 01/16] dt-bindings: usb: fix yamllint check warning Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 02/16] dt-bindings: usb: mediatek: " Chunfeng Yun
2021-02-09 20:46   ` Rob Herring
2021-02-01  7:00 ` [PATCH next v3 03/16] dt-bindings: phy: mediatek: dsi-phy: modify compatible dependence Chunfeng Yun
2021-02-09 20:47   ` Rob Herring
2021-02-12 14:40   ` Chun-Kuang Hu
2021-02-01  7:00 ` [PATCH next v3 04/16] dt-bindings: phy: mediatek: hdmi-phy: modify compatible items Chunfeng Yun
2021-02-09 20:48   ` Rob Herring
2021-02-12 14:41   ` Chun-Kuang Hu
2021-02-01  7:00 ` [PATCH next v3 05/16] dt-bindings: phy: mediatek: tphy: change patternProperties Chunfeng Yun
2021-02-09 20:49   ` Rob Herring
2021-02-01  7:00 ` [PATCH next v3 06/16] dt-bindings: usb: mtk-xhci: add optional assigned clock properties Chunfeng Yun
2021-02-09 20:49   ` Rob Herring
2021-02-01  7:00 ` [PATCH next v3 07/16] dt-bindings: usb: mtk-xhci: add compatible for mt2701 and mt7623 Chunfeng Yun
2021-02-09 20:50   ` Rob Herring
2021-02-01  7:00 ` [PATCH next v3 08/16] dt-bindings: usb: mediatek: musb: add mt8516 compatbile Chunfeng Yun
2021-02-09 20:51   ` Rob Herring
2021-02-01  7:00 ` [PATCH next v3 09/16] arm64: dts: mediatek: mt8173: fix dtbs_check warning Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 10/16] arm64: dts: mediatek: mt2712: harmonize node names Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 11/16] arm64: dts: mediatek: mt8516: harmonize node names and compatibles Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 12/16] arm64: dts: mediatek: mt7622: " Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 13/16] arm64: dts: mediatek: mt8183: fix dtbs_check warning Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 14/16] arm: dts: mt7629: harmonize node names and compatibles Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 15/16] arm: dts: mt7623: " Chunfeng Yun
2021-02-01  7:00 ` [PATCH next v3 16/16] arm: dts: mt2701: " Chunfeng Yun
2021-02-09 20:44 ` Rob Herring [this message]

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=20210209204412.GA139333@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=min.guo@mediatek.com \
    --cc=p.zabel@pengutronix.de \
    --cc=vkoul@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).