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][RESEND] RTC Device Driver Tests
Date: Thu, 25 Feb 2010 15:03:04 +0530 [thread overview]
Message-ID: <20100225093304.GA23984@linux.vnet.ibm.com> (raw)
In-Reply-To: <41c7690d1002250109r5e35b35cw2b10c0e270bc273a@mail.gmail.com>
On Thu, Feb 25, 2010 at 02:39:37PM +0530, Silesh C V wrote:
> >>
> >> The end goal is to have these tests fit directly into LTP without
> >> having to fudge around writing a secondary driver, thus maintaining
> >> two pieces of dependent code [which is of course more complicated than
> >> one piece of code], and thus is more of a pain to maintain longterm.
> >> There's a lot of code in the repository like this that was ported and
> >> subsequently not properly adapted to the existing infrastructure, thus
> >> creating additional headache for maintainers and end-users.
> >
> > Ok -- I take that back. I have no idea wtf is going on in this
> > directory nor the ultimate intent of the tests in here, apart from
> > being a lot of ad hoc pain in the arse-ness.
>
> The README in testcases/kernel/device-drivers/ says that these tests
> should not be run with the other tests, and they have to be built
> separately. I agree that this is because they have a kernel space part
> also. But this prevents us from building device_driver tests that
> have only user space part (as in RTC tests), along with the overall
> build. And these tests does not belong in any other directory other
> than kernel/device-drivers. So as long as other tests are there we
> will have to live with building new device driver tests separately.I
> can re-send the patch with Garrett's suggestions incorporated.
>
> Subrata, suggestions ?
Hi Silesh,
How about porting this on new makefile infrastructure ? I think this is
time where we can look back and can make one piece of code as garret
said is correct. Please see your fesibility. Let me know if you still
want this to be integrated. Before that can you please little more
descriptive with your patch e,g: what it is doing.
And also it is always good if you include more documentation for each
function as coding style suggests.
Thanks
Rishi
>
>
> Thanks,
> Silesh
> >
> > I've learned enough to keep my hands off this because it looks like a mess.
> >
> > Thanks,
> > -Garrett
> >
--
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net
------------------------------------------------------------------------------
Download Intel® 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
next prev parent reply other threads:[~2010-02-25 9:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 12:10 [LTP] [PATCH][RESEND] RTC Device Driver Tests Silesh C V
2010-02-24 21:14 ` Garrett Cooper
2010-02-25 6:40 ` Silesh C V
2010-02-25 7:07 ` Garrett Cooper
2010-02-25 7:11 ` Garrett Cooper
2010-02-25 9:09 ` Silesh C V
2010-02-25 9:33 ` Rishikesh K Rajak [this message]
2010-02-25 9:48 ` Garrett Cooper
2010-02-26 3:06 ` Silesh C V
2010-02-26 4:55 ` [LTP] [PATCH-v2] " Silesh C V
2010-02-26 5:31 ` Garrett Cooper
2010-02-26 6:39 ` Silesh C V
2010-02-26 5:34 ` Rishikesh K Rajak
2010-02-26 8:51 ` Rishikesh K Rajak
2010-02-26 9:11 ` Rishikesh K Rajak
2010-03-01 6:29 ` Rishikesh K Rajak
2010-03-02 9:47 ` Silesh C V
2010-03-03 4:59 ` Rishikesh K Rajak
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=20100225093304.GA23984@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