From: Anthony Liguori <aliguori@us.ibm.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: Xen-Devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 3/3] Some "make check" tests for xen/common
Date: Fri, 09 Dec 2005 09:52:42 -0600 [thread overview]
Message-ID: <4399A84A.4010104@us.ibm.com> (raw)
In-Reply-To: <20051209055625.GU25348@bakeyournoodle.com>
Hi Tony,
I've been trying out the make check/fullcheck and I'm very impressed! I
hope it gets pulled into the tree soon.
Two suggestions though, for patches this large, it would help to either
attach it to the original mail or provide a url to it. inlining is nice
for review but a pain to pull out and apply to a tree.
Also, with the latest unstable (8311:53cff3f88e45) the patches fail to
build (on xen/common/test/test_event_channel.c) because it cannot find
the include file <public/event_channel.h> in the #include
"../event_channel.c". I was able to work around this by adding
-I../../include to the build rule in the Makefile.
Otherwise, this stuff rocks!
Regards,
Anthony Liguori
Tony Breeds wrote:
>Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
>
>----- Forwarded message from Rusty Russell <rusty@rustcorp.com.au> -----
>
>To: Tony Breeds <tony@bakeyournoodle.com>
>From: Rusty Russell <rusty@rustcorp.com.au>
>Subject: [PATCH 3/3] Some "make check" tests for xen/common
>Date: Fri, 09 Dec 2005 16:47:43 +1100
>
>Some of these tests could probably be improved, but this is a first cut.
>Not all the files are tested yet, just enough to know we're on the right
>track.
>
>Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>
>
next prev parent reply other threads:[~2005-12-09 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 5:56 [PATCH 3/3] Some "make check" tests for xen/common Tony Breeds
2005-12-09 15:52 ` Anthony Liguori [this message]
2005-12-10 23:15 ` Tony Breeds
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=4399A84A.4010104@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=tony@bakeyournoodle.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.