From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] [RFC] cr_tests: Add eventfd01 test based on LTP test
Date: Tue, 27 Oct 2009 18:25:00 -0500 [thread overview]
Message-ID: <20091027232500.GA25328@us.ibm.com> (raw)
In-Reply-To: <4AE77B53.5090601-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
Quoting Oren Laadan (orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org):
>
>
> Serge E. Hallyn wrote:
> > Quoting Matt Helsley (matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
> >> Add checkpoint spots to the LTP test. Notably different from the
> >> epoll test library, these labels to not incorporate error handling
> >> code. Rather the test and branch are explicit and rely on LTP tst_*
> >> functions. As such it requires libltp.a to link. Do this with:
> >>
> >> make LTPROOT=/path/to/ltp/install
> >>
> >> Signed-off-by: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> >
> > Since it doesn't automatically run I just went ahead and applied
> > it. I'll get aroudn to testing when eventfd hits Oren's tree I
> > guess :)
>
> It's there since yesterday.
> I guess not much sleep for you tonight :)
>
> Oren.
Huh, so it is - for some reason i thought you were going
to wait until ckpt-v19 opened up. I guess that means I
have to go test :)
-serge
prev parent reply other threads:[~2009-10-27 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 22:29 [PATCH] [RFC] cr_tests: Add eventfd01 test based on LTP test Matt Helsley
[not found] ` <1256596171-11117-1-git-send-email-matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-27 20:56 ` Serge E. Hallyn
[not found] ` <20091027205648.GA19351-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-27 22:59 ` Oren Laadan
[not found] ` <4AE77B53.5090601-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-10-27 23:25 ` Serge E. Hallyn [this message]
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=20091027232500.GA25328@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org \
/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