devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Simon Horman <simon.horman@netronome.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	devicetree@vger.kernel.org,
	"David S . Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH v2] dt-bindings: net: mdio: remove compatible string from example
Date: Wed, 19 Feb 2020 14:09:26 -0600	[thread overview]
Message-ID: <20200219200926.GA21759@bogus> (raw)
In-Reply-To: <20200214194408.9308-1-grygorii.strashko@ti.com>

On Fri, 14 Feb 2020 21:44:08 +0200, Grygorii Strashko wrote:
> Remove vendor specific compatible string from example, otherwise DT YAML
> schemas validation may trigger warnings specific to TI ti,davinci_mdio
> and not to the generic MDIO example.
> 
> For example, the "bus_freq" is required for davinci_mdio, but not required for
> generic mdio example. As result following warning will be produced:
>  mdio.example.dt.yaml: mdio@5c030000: 'bus_freq' is a required property
> 
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
> Remove compatible string from example instead of changing it.
> 
> v1: https://patchwork.ozlabs.org/patch/1201674/
> 
>  Documentation/devicetree/bindings/net/mdio.yaml | 1 -
>  1 file changed, 1 deletion(-)
> 

Applied, thanks.

Rob

      reply	other threads:[~2020-02-19 20:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 19:44 [PATCH v2] dt-bindings: net: mdio: remove compatible string from example Grygorii Strashko
2020-02-19 20:09 ` 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=20200219200926.GA21759@bogus \
    --to=robh@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@netronome.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).