From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: dtc: Restore missing code for testcases
Date: Wed, 17 Oct 2007 07:11:29 -0500 [thread overview]
Message-ID: <E1Ii7kH-0002Jg-RQ@jdl.com> (raw)
In-Reply-To: Your message of "Wed, 17 Oct 2007 11:23:57 +1000." <20071017012357.GE28260@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> Recent commits 333542fabf8720b881e992a5abca32ef4bcb841a and
> fd1bf3a5ae46962528ef89a824261a88830758a2 added new testcases to dtc.
> However, although the testcases were added to the Makefile and
> run_tests.sh, one of the .c files for the testcase was omitted from
> the patch in each case.
>
> This patch restores the missing testcase code.
>
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>
Applied.
> jdl, you should
> really run a "make check" before committing my patches...
In the past, I have. I confess, this last round I only
compiled tested things. I'm really still catching up some...
jdl
prev parent reply other threads:[~2007-10-17 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 1:23 dtc: Restore missing code for testcases David Gibson
2007-10-17 12:11 ` 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=E1Ii7kH-0002Jg-RQ@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