354ebb48db8e66a853a58379a4808d5dcd1ceac3 |
|
07-Dec-2012 |
Wanlong Gao <gaowanlong@cn.fujitsu.com> |
cleanup code indent Cleanup the code indent using: find . -name *.c -exec Lindent {} \; It's really a big change, but can fix almost all of the indent problem in C code, although we can't ensure all of the changes are right, but the error changes are really few. Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
4548c6cf9bcdd96d8303caa4130ab638b61f8a30 |
|
19-Oct-2012 |
Wanlong Gao <gaowanlong@cn.fujitsu.com> |
Update FSF address find . -type f -exec sed -i 's/675 Mass Ave, Cambridge, MA 02139, USA/51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA/g' {} \; find . -type f -exec sed -i 's/59 Temple Place, Suite 330, Boston, MA 02111-1307 USA/51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA/g' {} \; Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
ec6edca7aa42b6affd989ef91b5897f96795e40f |
|
18-Oct-2012 |
Chris Dearman <chris@mips.com> |
Add missing newline at end of file This is a scripted change done using the following command: find . -type d -name .git -prune -o \ -type f \! -name \*\~ \! -name .\#\* \ \! -name \*.gz \! -name \*.pdf \! -name \*.patch -print0 | \ xargs -0 sed -i -e '$a\' Signed-off-by: Chris Dearman <chris@mips.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
2c28215423293e443469a07ae7011135d058b671 |
|
16-Dec-2010 |
Garrett Cooper <yanegomi@gmail.com> |
Style and conformance changes. 1. Strip all leading space. 2. Move tst_exit() to main(). 3. Remove tst_exit() from cleanup(). 4. Remove cluebat comments. 5. Reduce some unnecessary whitespace. Signed-off-by: Garrett Cooper <yanegomi@gmail.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
8fb1cdb0538640f295691929650408688537fb7f |
|
29-Nov-2010 |
Garrett Cooper <yanegomi@gmail.com> |
More style cleanup. Do a better job at detecting spurious leading and trailing whitespace in branches and loop statements. Signed-off-by: Garrett Cooper <yanegomi@gmail.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
df3eb16e38c6a163b0a7367c885679eed6140964 |
|
29-Nov-2010 |
Garrett Cooper <yanegomi@gmail.com> |
Deal with a lot of annoying style nits. Signed-off-by: Garrett Cooper <yanegomi@gmail.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
bdbaec51a423e715c2b03ed9e497e9a1fba6103e |
|
26-Feb-2009 |
subrata_modak <subrata_modak> |
Clean Trailing Tab: Signed-off-by: Michal Simek <monstr@monstr.eu>.
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
4bb656a129f7507823e9e6d6b98b1a02fd80ef89 |
|
26-Feb-2009 |
subrata_modak <subrata_modak> |
Clear Trailing Whitespace. Signed-off-by: Michal Simek <monstr@monstr.eu>.
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
083473cbf0610a7c169b2e584bfab862bd15af0f |
|
10-Sep-2008 |
subrata_modak <subrata_modak> |
Fix memory leak in time-schedule. Use valgrind tool (http://valgrind.org/) to check the memory leak problem. Now the valgrind can be compiled on the following platforms: X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux. ================= Before patching ================= # valgrind --leak-check=full ./time-schedule .................... ==17837== LEAK SUMMARY: ==17837== definitely lost: 20,440 bytes in 1 blocks. ==17837== possibly lost: 0 bytes in 0 blocks. ==17837== still reachable: 0 bytes in 0 blocks. ==17837== suppressed: 0 bytes in 0 blocks. ================= After patching ================= # valgrind --leak-check=full --show-reachable=yes ./time-schedule ................... ==18224== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1) ==18224== malloc/free: in use at exit: 0 bytes in 0 blocks. ==18224== malloc/free: 249 allocs, 249 frees, 240,112 bytes allocated. ==18224== For counts of detected errors, rerun with: -v ==18224== All heap blocks were freed -- no leaks are possible. Signed-off-by: Jin Bing Guo <guojb@cn.ibm.com>
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
477f4f1bcdef98fbe9c064615cb8b5cee5f3bc98 |
|
27-Aug-2008 |
subrata_modak <subrata_modak> |
In testcases/kernel/sched/tool/time-schedule, it used kill(0, SIGTERM) to terminate the all the processes in the group. However, the progress group leader might be different regarding the different call methods. In interactive call such as pan, it called time-schedule by exec() and setpgrp() as a child process. The time-schedule process would be the process group leader and all the child processes created by it had the same PGID. So the SIGTERM was sent to process group and the exit code got by pan was 0. In non-inactive call such as STAF/STAX, one shell script called the time-schedule directly. The shell script would be the process group leader. So the SIGTERM was also sent to the shell script and the exit code got by STAF/STAX was 143 (128+15). This patch can resolve this problem. Signed-off-by: Lin Feng Shen <shenlinf@cn.ibm.com>, Signed-off-by: Jin Bing Guo <guojb@cn.ibm.com>.
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
e909dfc26f7957be5724315e73049f1bee8671b5 |
|
03-Jun-2008 |
subrata_modak <subrata_modak> |
time-schedule01 failed, because it sent SIGTERM to itself before program exited, so the return value is not 0. This patch makes the main process ignore SIGTERM. Li Zefan <lizf@cn.fujitsu.com>.
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
5e9c69e9a2c8ac10b2f3a2e526e3bb67cf9f59f3 |
|
04-Sep-2002 |
nstraz <nstraz> |
Applying patch from Steven J. Hill <sjhill@realitydiluted.com>. This patch removes the deprecated use of 'sys_errlist' to use 'strerror' instead. Please apply. Thanks. -Steve
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|
962503adca422e5a8b886997e60202c3c0f13606 |
|
26-Feb-2002 |
iyermanoj <iyermanoj> |
Checkin in the testcase after getting approval from the author. I also executed the sourcescreen(ver 1.3) tool and manually inspected the testcase to see if it is clean. Output of the tool is as follows... => ./screensource.sh time-schedule.c --time-schedule.c: 8: it under the terms of the GNU General Public License as published by 9: the Free Software Foundation; either version 2 of the License, or 15: GNU General Public License for more details. 17: You should have received a copy of the GNU General Public License License:License agreement referenced. Looks safe! :q ----------------------------------
/external/ltp/testcases/kernel/sched/tool/time-schedule.c
|