public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Silesh C V <saileshcv@gmail.com>
Cc: ltp-list@lists.sourceforge.net, Arun.sudhilal@lntinfotech.com,
	Mohamed.Rasheed@lntinfotech.com
Subject: Re: [LTP] [PATCH-v3] RTC Device Driver Tests
Date: Thu, 4 Mar 2010 18:25:14 +0530	[thread overview]
Message-ID: <20100304125514.GA21634@linux.vnet.ibm.com> (raw)
In-Reply-To: <41c7690d1003032130i6b61968bjc175698937dc0051@mail.gmail.com>

>Rishi,

>Can you test this patch on the machine on which the tests got stuck
>earlier?

Yes i tested and found that, it is failing.

[root@x335a rtc]# ./rtc-test /dev/rtc 
rtc01       0  TINFO  :  RTC READ TEST:
rtc01       1  TPASS  :  RTC READ TEST Passed
rtc01       0  TINFO  :  Current Date/time is  03/03/10 12:38:26 PM
rtc01       0  TINFO  :  RTC ALARM TEST :
rtc01       0  TINFO  :  Alarm time set to 12:38:31.
rtc01       0  TINFO  :  Waiting 5 seconds for the alarm...
rtc01       2  TFAIL  :  Timed out waiting for the alarm
rtc01       0  TINFO  :  RTC UPDATE INTERRUPTS TEST :
rtc01       0  TINFO  :  Waiting for  5 update interrupts...
rtc01       0  TINFO  :  Update interrupt 1
rtc01       0  TINFO  :  Update interrupt 2
rtc01       0  TINFO  :  Update interrupt 3
rtc01       0  TINFO  :  Update interrupt 4
rtc01       0  TINFO  :  Update interrupt 5
rtc01       3  TPASS  :  RTC UPDATE INTERRUPTS TEST Passed
rtc01       0  TINFO  :  RTC Tests Done!
[root@x335a rtc]# ls -l /dev/rtc*
crw-r--r-- 1 root root 10, 135 Feb 20 13:51 /dev/rtc
[root@x335a rtc]# 



In fact while compiling there is some warning also.
[root@x335a rtc]# make
cc rtc-test.c -O2 -Wall -I ../../../../include/ -L ../../../../lib/
-lltp  -o rtc-test
rtc-test.c: In function ‘read_alarm_test’:
rtc-test.c:64: warning: dereferencing type-punned pointer will break
strict-aliasing rules

Please solve these problems and please send me a revised patch.

-- 
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-03-04 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  5:30 [LTP] [PATCH-v3] RTC Device Driver Tests Silesh C V
2010-03-04 12:55 ` Rishikesh K Rajak [this message]
2010-03-05  5:54   ` Silesh C V
2010-03-05  6:14     ` Garrett Cooper
2010-03-05  6:54       ` Silesh C V
2010-03-05  7:04         ` Garrett Cooper
2010-03-05  8:34           ` Silesh C V
2010-03-05 10:51             ` Garrett Cooper
2010-03-06  6:15               ` Silesh C V

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=20100304125514.GA21634@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=Arun.sudhilal@lntinfotech.com \
    --cc=Mohamed.Rasheed@lntinfotech.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=saileshcv@gmail.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