devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	David Jander <david@protonic.nl>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: vendor-prefixes: add "virtual" prefix
Date: Tue, 17 Nov 2020 11:39:57 +0100	[thread overview]
Message-ID: <87fb8903-662e-572d-1a74-d0d5bc2fa49b@pengutronix.de> (raw)
In-Reply-To: <20201117103857.6089-2-o.rempel@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1441 bytes --]

On 11/17/20 11:38 AM, Oleksij Rempel wrote:
> "virtual" is used for vendor-less "devices". For example for the GPIO
> based MDIO bus "virtual,mdio-gpio".
> 
> This patch is needed to fix the checkpatch warning for the Protonic WD3 board.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index d3454100e94e..365ac2fedd7d 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1160,6 +1160,8 @@ patternProperties:
>      description: Videostrong Technology Co., Ltd.
>    "^virtio,.*":
>      description: Virtual I/O Device Specification, developed by the OASIS consortium
> +  "^virtual,.*":
> +    description: Used for virtula device without specific vendor.
                             ^^^^^^^

typo


>    "^vishay,.*":
>      description: Vishay Intertechnology, Inc
>    "^vitesse,.*":
> 

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-11-17 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 10:38 [PATCH v3 0/3] mainline Protonic WD3 board Oleksij Rempel
2020-11-17 10:38 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: add "virtual" prefix Oleksij Rempel
2020-11-17 10:39   ` Marc Kleine-Budde [this message]
2020-11-17 10:38 ` [PATCH v3 2/3] dt-bindings: arm: fsl: add Protonic WD3 board Oleksij Rempel
2020-11-17 10:38 ` [PATCH v3 3/3] ARM: dts: " Oleksij Rempel
2020-11-17 10:45   ` Marc Kleine-Budde

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=87fb8903-662e-572d-1a74-d0d5bc2fa49b@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=david@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=o.rempel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).