devicetree-compiler.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: Julia Lawall <Julia.Lawall-L2FTfq7BK8M@public.gmane.org>,
	devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/3] checks: failure message improvements
Date: Wed, 31 Jan 2018 08:57:02 -0600	[thread overview]
Message-ID: <20180131145705.21335-1-robh@kernel.org> (raw)

This series standardizes how node paths and property names are printed 
in failure messages and switches to using source file and line numbers 
for failure messages.

The first 2 patches can apply to master. The 3rd is dependent on Julia's 
source annotation series.

Rob

Rob Herring (3):
  checks: centralize printing of node path in check_msg
  checks: centralize printing of property names in failure messages
  checks: Use source position information for check failures

 checks.c | 276 +++++++++++++++++++++++++++++++--------------------------------
 1 file changed, 136 insertions(+), 140 deletions(-)

-- 
2.14.1

             reply	other threads:[~2018-01-31 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 14:57 Rob Herring [this message]
     [not found] ` <20180131145705.21335-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-31 14:57   ` [PATCH 1/3] checks: centralize printing of node path in check_msg Rob Herring
     [not found]     ` <20180131145705.21335-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-02-09  6:53       ` David Gibson
2018-01-31 14:57   ` [PATCH 2/3] checks: centralize printing of property names in failure messages Rob Herring
     [not found]     ` <20180131145705.21335-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-02-10  1:09       ` David Gibson
2018-01-31 14:57   ` [PATCH 3/3] checks: Use source position information for check failures Rob Herring

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