From: Gilles Carry <Gilles.Carry@bull.net>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: subrata@linux.vnet.ibm.com, Sripathi Kodi <sripathik@in.ibm.com>,
dvhltc <dvhltc@linux.vnet.ibm.com>, tinytim <tinytim@us.ibm.com>,
Nivedita Singhvi <niv@us.ibm.com>,
Chirag Jog <chirag@linux.vnet.ibm.com>,
Ankita Garg <ankita@in.ibm.com>, dino <dino@linux.vnet.ibm.com>,
Sebastien Dugue <sebastien.dugue@bull.net>,
Jean-Pierre Dion <jean-pierre.dion@bull.net>,
Michael Olbrich <m.olbrich@pengutronix.de>,
Robert Schwebel <r.schwebel@pengutronix.de>,
ltp-list <ltp-list@lists.sourceforge.net>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [LTP] realtime run shellscripts suite - question 1
Date: Fri, 16 May 2008 08:18:04 +0200 [thread overview]
Message-ID: <482D271C.2040108@bull.net> (raw)
In-Reply-To: <1210890820.26549.17.camel@Aeon>
Darren Hart wrote:
> On Thu, 2008-05-15 at 13:34 +0200, Gilles Carry wrote:
>
>>Here it is:
>>
>>perf/latency
>>func/hrtimer-prio
>>func/measurement
>>have a run.sh instead of a run_auto.sh and therefore cannot be reached
>>by ./run.sh -t all
>>Is this intentional or shall I rename them as run_auto.sh?
>>
>
>
> The reason being (iirc) that we didn't want to include those in the
> automatic run from the top level. the individual run.sh must be run
> automatically.
OK. I'll make a separate patch for moving these to run_auto.sh.
Gilles.
prev parent reply other threads:[~2008-05-16 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4829A2B7.2010200@bull.net>
2008-05-14 7:30 ` [LTP] realtime run shellscripts suite - anyone using it? Subrata Modak
2008-05-15 6:01 ` Sripathi Kodi
[not found] ` <200805151131.29082.sripathik-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
2008-05-15 6:48 ` Subrata Modak
2008-05-15 6:57 ` [LTP] " Gilles Carry
2008-05-15 7:00 ` Subrata Modak
2008-05-15 11:34 ` [LTP] realtime run shellscripts suite - question 1 Gilles Carry
2008-05-15 22:33 ` Darren Hart
2008-05-16 6:18 ` Gilles Carry [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=482D271C.2040108@bull.net \
--to=gilles.carry@bull.net \
--cc=ankita@in.ibm.com \
--cc=chirag@linux.vnet.ibm.com \
--cc=dino@linux.vnet.ibm.com \
--cc=dvhltc@linux.vnet.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=jean-pierre.dion@bull.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=m.olbrich@pengutronix.de \
--cc=niv@us.ibm.com \
--cc=r.schwebel@pengutronix.de \
--cc=sebastien.dugue@bull.net \
--cc=sripathik@in.ibm.com \
--cc=subrata@linux.vnet.ibm.com \
--cc=tinytim@us.ibm.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 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.