netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Kurt Kanzenbach <kurt@kmk-computers.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	kurt@linutronix.de
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: dsa: b53: Add YAML bindings
Date: Sat, 10 Oct 2020 19:28:51 -0700	[thread overview]
Message-ID: <3249c764-ec4a-26be-a52d-e9e85f3162ea@gmail.com> (raw)
In-Reply-To: <20201010164627.9309-2-kurt@kmk-computers.de>



On 10/10/2020 9:46 AM, Kurt Kanzenbach wrote:
> Convert the b53 DSA device tree bindings to YAML in order to allow
> for automatic checking and such.
> 
> Suggested-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Kurt Kanzenbach <kurt@kmk-computers.de>

Thanks for making this change, there are quite a few warnings that are 
going to show up because the binding was defined in a way that it would 
define chip compatible strings, which not all DTS files are using. I 
don't know if Rob would be comfortable with taking this until we resolve 
all warnings first.
-- 
Florian

  reply	other threads:[~2020-10-11  2:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 16:46 [PATCH net-next 0/2] dt-bindings: net: dsa: b53: Add YAML bindings Kurt Kanzenbach
2020-10-10 16:46 ` [PATCH net-next 1/2] " Kurt Kanzenbach
2020-10-11  2:28   ` Florian Fainelli [this message]
2020-10-11  8:32     ` Kurt Kanzenbach
2020-10-11 15:46       ` Florian Fainelli
2020-10-12  5:45         ` Kurt Kanzenbach
2020-10-12 18:48           ` Rob Herring
2020-10-10 16:46 ` [PATCH net-next 2/2] dt-bindings: net: dsa: b53: Drop old bindings Kurt Kanzenbach
2020-10-12 18:47   ` Rob Herring
2020-10-15  7:05     ` Kurt Kanzenbach
2020-10-16  2:43       ` Florian Fainelli

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=3249c764-ec4a-26be-a52d-e9e85f3162ea@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=kurt@kmk-computers.de \
    --cc=kurt@linutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=vivien.didelot@gmail.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).