linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: dtc: Flexible tree checking infrastructure (v2)
Date: Tue, 27 Nov 2007 14:58:29 +1100	[thread overview]
Message-ID: <20071127035829.GB12051@localhost.localdomain> (raw)
In-Reply-To: <E1IwmCq-0002g9-Nk@jdl.com>

On Mon, Nov 26, 2007 at 04:13:32PM -0600, Jon Loeliger wrote:
> So, like, the other day David Gibson mumbled:
> > dtc: Flexible tree checking infrastructure
> > 
> > Here, at last, is a substantial start on revising dtc's infrastructure
> > for checking the tree; this is the rework I've been saying was
> > necessary practically since dtc was first release.
> > 
> > In the new model, we have a table of "check" structures, each with a
> > name, references to checking functions, and status variables.  Each
> > check can (in principle) be individually switched off or on (as either
> > a warning or error).  Checks have a list of prerequisites, so if
> > checks need to rely on results from earlier checks to make sense (or
> > even to avoid crashing) they just need to list the relevant other
> > checks there.
> > 
> > For now, only the "structural" checks and the fixups for phandle
> > references are converted to the new mechanism.  The rather more
> > involved semantic checks (which is where this new mechanism will
> > really be useful) will have to be converted in future patches.
> > 
> > At present, there's no user interface for turning on/off the checks -
> > the -f option now forces output even if "error" level checks fail.
> > Again, future patches will be needed to add the fine-grained control,
> > but that should be quite straightforward with the infrastructure
> > implemented here.
> > 
> > Also adds a testcase for the handling of bad references, which catches
> > a bug encountered while developing this patch.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> 
> While I've Applied this one, it has introduced this:
> 
>          CC dtc.o
>     dtc.c: In function 'main':
>     dtc.c:199: warning: 'structure_ok' is used uninitialized in this function
> 
> Followup easy patch?

Crap.  For some reason my compiler isn't giving that warning, so I
missed that little bug :(.

I'm away at the moment, I'll see what I can do.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2007-11-27  3:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  5:38 dtc: Flexible tree checking infrastructure David Gibson
2007-11-22  3:38 ` dtc: Flexible tree checking infrastructure (v2) David Gibson
2007-11-26 22:13   ` Jon Loeliger
2007-11-27  3:58     ` David Gibson [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=20071127035829.GB12051@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.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).