devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/3] dtc bus and unit address checks
Date: Tue, 28 Feb 2017 16:43:07 -0600	[thread overview]
Message-ID: <20170228224310.14162-1-robh@kernel.org> (raw)

This is a series of checks designed to check problems commonly found in
binding reviews. The first patch adds checks for PCI bridges and devices.
The 2nd patch is new in this version and adds checks for simple-bus. The
3rd patch is a default check if bus type is not set to check for '0x' or
leading 0s in unit addresses.

Rob

Rob Herring (3):
  checks: Add bus checks for PCI buses
  checks: Add bus checks for simple-bus buses
  checks: Warn on node name unit-addresses with '0x' or leading 0s

 checks.c                       | 230 +++++++++++++++++++++++++++++++++++++++++
 dtc.h                          |   5 +
 tests/run_tests.sh             |   2 +
 tests/unit-addr-leading-0s.dts |  12 +++
 tests/unit-addr-leading-0x.dts |  12 +++
 5 files changed, 261 insertions(+)
 create mode 100644 tests/unit-addr-leading-0s.dts
 create mode 100644 tests/unit-addr-leading-0x.dts

-- 
2.10.1

             reply	other threads:[~2017-02-28 22:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 22:43 Rob Herring [this message]
     [not found] ` <20170228224310.14162-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-02-28 22:43   ` [PATCH v3 1/3] checks: Add bus checks for PCI buses Rob Herring
     [not found]     ` <20170228224310.14162-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-03-03  2:09       ` David Gibson
2017-02-28 22:43   ` [PATCH v3 2/3] checks: Add bus checks for simple-bus buses Rob Herring
     [not found]     ` <20170228224310.14162-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-03-03  2:12       ` David Gibson
     [not found]         ` <20170303021206.GD4067-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-03-06 10:48           ` Rob Herring
     [not found]             ` <CAL_JsqJzWAiBUZeRMx0i5Y_NAFH6_jrASWcFp_U4MwVf2+=h0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-07  3:41               ` David Gibson
     [not found]                 ` <20170307034110.GC19967-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2017-03-07 13:39                   ` Rob Herring
2017-03-07 13:51                   ` Rob Herring
     [not found]                     ` <CAL_Jsq+U4SqL2EDR6hRrE_JcONkfkZqacBQGz4Kkq=CxNbaYAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-08  1:55                       ` David Gibson
2017-02-28 22:43   ` [PATCH v3 3/3] checks: Warn on node name unit-addresses with '0x' or leading 0s Rob Herring
     [not found]     ` <20170228224310.14162-4-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-03-03  2:12       ` David Gibson

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=20170228224310.14162-1-robh@kernel.org \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).