From: jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH 0 of 2] [v2] Another attempt to Consolidate x86 makefiles & tests
Date: Tue, 23 Oct 2007 22:26:38 -0500 [thread overview]
Message-ID: <patchbomb.1193196398@thinkpad> (raw)
This is the acutally the 3rd attempt.
These patches consolidate the make files & tests in user director for x86. This
is to allow other architectures easier integration into the kvm source.
Signed-off-by: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-24 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 3:26 jyoung5-r/Jw6+rmf7HQT0dZR+AlfA [this message]
2007-10-24 3:26 ` [PATCH 1 of 2] consolidate x86 user makefiles jyoung5-r/Jw6+rmf7HQT0dZR+AlfA
2007-10-24 14:32 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-24 3:26 ` [PATCH 2 of 2] Move all x86 specific tests to there own directory jyoung5-r/Jw6+rmf7HQT0dZR+AlfA
2007-10-24 14:32 ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-25 18:12 ` [PATCH 0 of 2] [v2] Another attempt to Consolidate x86 makefiles & tests Avi Kivity
[not found] ` <4720DC70.6090607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 18:37 ` userspace repositories Hollis Blanchard
2007-10-25 18:40 ` Avi Kivity
[not found] ` <4720E312.3060400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-25 19:01 ` Hollis Blanchard
2007-10-25 19:03 ` Avi Kivity
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=patchbomb.1193196398@thinkpad \
--to=jyoung5-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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