From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Jiri Palecek <jpalecek@web.de>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] New test?
Date: Mon, 26 Oct 2009 22:33:10 +0530 [thread overview]
Message-ID: <1256576590.4929.61.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <364299f40910252049g2b30f5afq1f689ccbb820e05b@mail.gmail.com>
On Sun, 2009-10-25 at 20:49 -0700, Garrett Cooper wrote:
> 2009/10/25 Jiří Paleček <jpalecek@web.de>:
> > On Sun, 18 Oct 2009 20:22:00 +0200, Subrata Modak
> > <subrata@linux.vnet.ibm.com> wrote:
> >
> >> Jiri,
> >>
> >> Any further thoughts on this ?
> >
> > Yes, see the attachment.
> >
> > I created the directories for the different tests (rt_sigtimedwait,
> > sigwaitinfo etc.), but to avoid copy-pasting the code, they share the same
> > source. Please, tell me if that is OK.
> >
> > Regards
> > Jiri Palecek
> >>
> >> On Tue, 2009-10-13 at 17:43 +0530, Subrata Modak wrote:
> >>>
> >>> Hey Jiri,
> >>>
> >>> On Tue, 2009-09-29 at 16:28 +0200, Jiří Paleček wrote:
> >>> > Hello,
> >>> >
> >>> > I've decided to create a test for the rt_sigwaitinfo syscall. There are
> >>> > other functions with similar interface (defined by POSIX) in libc -
> >>> > particularly sigwait, sigtimedwait and sigwaitinfo. The rt_sigwaitinfo
> >>>
> >>> The sigwait, sigtimedwait and sigwaitinfo testcases are not in LTP.
> >>>
> >>> > test could easily tests these too, so I wonder whether we want to test
> >>> > these too, and if yes, whether these tests can be located in the same
> >>> > executable.
> >>>
> >>> If you already have the logic to write the above tests, then please
> >>> create separate tests for sigwait, sigtimedwait and sigwaitinfo
> >>> (separate directories as well), and separate for rt_sigwaitinfo syscall.
> >>>
> >>> Regards--
> >>> Subrata
>
> The Makefiles need to be rewritten because a) they don't use the
> new infrastructure, and b) they break requirements for
> out-of-build-tree support. Please read README.mk-devel and ping me
As Garret says. He has done huge hard work on the Makefile.
Regards--
Subrata
> with any questions you may have.
> Thanks,
> -Garrett
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-10-26 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 14:28 [LTP] New test? Jiří Paleček
2009-10-13 12:13 ` Subrata Modak
2009-10-18 18:22 ` Subrata Modak
2009-10-26 0:43 ` Jiří Paleček
2009-10-26 3:49 ` Garrett Cooper
2009-10-26 17:03 ` Subrata Modak [this message]
2009-10-27 9:29 ` Jiří Paleček
2009-10-27 23:06 ` Garrett Cooper
2009-10-30 10:56 ` Jiří Paleček
2009-10-30 11:21 ` Garrett Cooper
2009-10-30 11:24 ` Garrett Cooper
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=1256576590.4929.61.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=jpalecek@web.de \
--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