From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: dtc: Add testcases for tree checks
Date: Tue, 20 Nov 2007 09:09:17 -0600 [thread overview]
Message-ID: <E1IuUiz-00022Y-E1@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 20 Nov 2007 16:24:23 +1100." <20071120052423.GC4356@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> This patch adds a group of testcases to check that dtc correctly
> rejects trees with various structural errors.
>
> To make things easier to test, we change dtc so that failing checks
> (as opposed to other errors) result in exit code 2.
>
> This patch also fixes an embarrasing bug uncovered by these new tests:
> check_phandles() worked out if the tree's phandles were valid, then
> throws that information away and returns success always.
>
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>
>
> NOTE! jdl, you'll need to chmod +x tests/dtc-checkfails.sh before you
> git commit this - it's a new shell script and patch can't encode the
> permissions info.
>
> Index: dtc/tests/dup-nodename.dts
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ dtc/tests/dup-nodename.dts 2007-11-20 16:02:22.000000000 +1100
Actually, this is the official third time now that it would have
been significantly nicer had you been using git for patches as
it does correctly handle excute permissions properly in patches.
And, it allows for side-band commentary such as your NOTE!, above,
to be included in the patch mail, but not in the patch log itself
such that it too doesn't have to be "git commit --amend"'ed out
as well.
In any event, Applied and Adjusted.
jdl
next prev parent reply other threads:[~2007-11-20 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 5:24 dtc: Add testcases for tree checks David Gibson
2007-11-20 15:09 ` Jon Loeliger [this message]
2007-11-20 22:03 ` David Gibson
2007-11-20 22:22 ` Jon Loeliger
2007-11-20 22:23 ` Scott Wood
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=E1IuUiz-00022Y-E1@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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