From: Jon Loeliger <jdl@jdl.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
Matt Porter <mporter@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@calxeda.com>,
Russ Dill <Russ.Dill@ti.com>
Subject: Re: Fix test relying in wrong behavior of is_printable
Date: Mon, 07 Jan 2013 08:30:03 -0600 [thread overview]
Message-ID: <E1TsDiF-0001dJ-0g@jdl.com> (raw)
In-Reply-To: <6BBCA320-AB8C-4DE3-BF98-3A77B1E94982@antoniou-consulting.com>
> Err,
>
> I can rework and resubmit to remove the comment, but the test doesn't =
> fail:
>
> > $ make check | grep 'MyBoardName.*-t s.*compatible'
> > fdtget-runtest.sh MyBoardName MyBoardFamilyName -t s label01.dts.fdtget.test.dtb / compatible: PASS
> >
>
> As of today's pull.
My build yields:
$ make check 2>&1 | grep FAIL
fdtget-runtest.sh 77 121 66 111 97 114 100 78 97 109 101 0 77 121 66 111 97 114 100 70 97 109 105 108 121 78 97 109 101 0 label01.dts.fdtget.test.dtb / compatible: FAIL Results differ from expected
* FAIL: 1
HTH,
jdl
next prev parent reply other threads:[~2013-01-07 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 19:16 Fix test relying in wrong behavior of is_printable Pantelis Antoniou
[not found] ` <1357326968-13124-1-git-send-email-panto-wVdstyuyKrO8r51toPun2/C9HSW9iNxf@public.gmane.org>
2013-01-06 3:58 ` David Gibson
[not found] ` <20130106035809.GG4674-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2013-01-06 11:41 ` Pantelis Antoniou
2013-01-06 22:14 ` Jon Loeliger
2013-01-07 9:55 ` Pantelis Antoniou
2013-01-07 14:30 ` Jon Loeliger [this message]
[not found] ` <5B13DF52-26BE-4BA1-8BD7-25863B04A3B6-wVdstyuyKrO8r51toPun2/C9HSW9iNxf@public.gmane.org>
2013-01-08 8:37 ` David Gibson
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=E1TsDiF-0001dJ-0g@jdl.com \
--to=jdl@jdl.com \
--cc=Russ.Dill@ti.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@ti.com \
--cc=panto@antoniou-consulting.com \
--cc=rob.herring@calxeda.com \
/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).