All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: dtc: Disable semantic checks by default
Date: Mon, 22 Oct 2007 11:39:01 -0500	[thread overview]
Message-ID: <E1Ik0Iv-0002yQ-2c@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 18 Oct 2007 17:22:30 +1000." <20071018072230.GA10392@localhost.localdomain>

So, like, the other day David Gibson mumbled:
> At present, dtc makes a lot of semantic checks on the device tree by
> default, and will refuse to produce output if they fail.  This means
> people tend to need -f to force output despite failing semantic checks
> rather a lot.
> 
> This patch splits the device tree checks into structural checks (no
> bad or duplicate names or phandles) and semantic checks (everything
> else).  By default, only the structural checks are performed, and are
> fatal.  -f will force output even with structural errors (using this
> in -Idts mode would essentially always be a bad idea, but it might be
> useful in -Idtb mode for examining a malformed dtb).
> 
> Semantic checks are only performed if the new -c command line option
> is supplied, and are always warnings only.  Semantic checks will never
> be performed on a tree with structural errors.
> 
> This patch is only a stopgap before implementing proper fine-grained
> error/warning handling, but it should at least get rid of the
> far-too-frequent need for -f for the time being.
> 
> This patch removes the -f from the dtc testcases now that it's no
> longer necessary.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

jdl

      reply	other threads:[~2007-10-22 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  7:22 dtc: Disable semantic checks by default David Gibson
2007-10-22 16:39 ` Jon Loeliger [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=E1Ik0Iv-0002yQ-2c@jdl.com \
    --to=jdl@jdl.com \
    --cc=david@gibson.dropbear.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.