From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: poky@yoctoproject.org
Cc: paul.eggleton@linux.intel.com,
openembedded-core@lists.openembedded.org,
georgex.l.musat@intel.com, benjamin.esquivel@intel.com
Subject: [PATCH 3/3] Update dev-manual to point to the new ptest-runner2.
Date: Thu, 14 Jan 2016 16:27:04 -0600 [thread overview]
Message-ID: <bae3519051fc355e6fdd7dc49eb80a100b56e1d2.1452808373.git.anibal.limon@linux.intel.com> (raw)
In-Reply-To: <cover.1452808370.git.anibal.limon@linux.intel.com>
In-Reply-To: <cover.1452808370.git.anibal.limon@linux.intel.com>
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
---
documentation/dev-manual/dev-manual-common-tasks.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index dbf493a..767f51c 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -7488,8 +7488,8 @@
<title>Running ptest</title>
<para>
- The <filename>ptest-runner</filename> package installs a
- shell script that loops through all installed ptest test
+ The <filename>ptest-runner2</filename> package installs a
+ program that loops through all installed ptest test
suites and runs them in sequence.
Consequently, you might want to add this package to
your image.
--
2.1.4
next prev parent reply other threads:[~2016-01-14 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 22:27 [PATCH 0/3] ptest-runner2 C implementation Aníbal Limón
2016-01-14 22:27 ` [PATCH 1/3] ptest-runner2: Add new ptest-runner2 recipe Aníbal Limón
2016-01-14 22:27 ` [PATCH 2/3] ptests: Update references to new ptest-runner2 Aníbal Limón
2016-01-14 22:27 ` Aníbal Limón [this message]
2016-01-18 15:52 ` [PATCH 0/3] ptest-runner2 C implementation Aníbal Limón
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=bae3519051fc355e6fdd7dc49eb80a100b56e1d2.1452808373.git.anibal.limon@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=benjamin.esquivel@intel.com \
--cc=georgex.l.musat@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.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