public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Silesh Vellattu <Silesh.Vellattu@lntinfotech.com>
Cc: ltp-list@lists.sourceforge.net,
	Arun Sudhilal <Arun.Sudhilal@lntinfotech.com>,
	Mohamed Rasheed <Mohamed.Rasheed@lntinfotech.com>
Subject: Re: [LTP] Device Driver Test cases for LTP
Date: Tue, 23 Feb 2010 14:45:39 +0530	[thread overview]
Message-ID: <4B839CBB.8090500@linux.vnet.ibm.com> (raw)
In-Reply-To: <EB1A7C66AD0C92419BFFC785A947865A09EA8C4BD6@BLRINMSMBX01.bglrodc.lntinfotech.com>

Silesh Vellattu wrote:
> Hi Subrata ,
>
>      We have been using LTP to test our kernel releases.Thanks for integrating such a test suite.But we can see that there are only limited number of interfaces (usb and V4L2) covered in the device driver test cases. We have  some test cases covering Audio  and RTC  which we have been using along with LTP and  we would like to contribute them to the LTP community.We have already integrated them to the LTP framework in a very generic  way. We also have plans to work on some other interfaces to make our testing process better.We would like to contribute those tests also as and when they are ready. Suggestions on how these test cases have to be written/ organised and how they can be integrated with LTP?
>   

That's great. Just go ahead and submit a patch along with the test 
results. Make the documentation clear of how to build/install and run 
those tests. Rishi will help you in integrating the same to LTP.

Regards--
Subrata

> Thanks and Warm Regards,
> Silesh.
>
> This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
>
> ______________________________________________________________________
>   



------------------------------------------------------------------------------
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-02-23  9:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <EB1A7C66AD0C92419BFFC785A947865A09EA8C4BD6@BLRINMSMBX01.bglrodc.lntinfotech.com>]

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=4B839CBB.8090500@linux.vnet.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=Arun.Sudhilal@lntinfotech.com \
    --cc=Mohamed.Rasheed@lntinfotech.com \
    --cc=Silesh.Vellattu@lntinfotech.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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