public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-ppc-devel] [PATCH 1 of 2] [mq]:	x86_user_make_changes
Date: Tue, 23 Oct 2007 21:55:56 -0500	[thread overview]
Message-ID: <1193194556.5807.0.camel@thinkpad> (raw)
In-Reply-To: <1193173823.22407.34.camel@basalt>

ok I can resend this anyway . I forgot to consolidate the kvmctl stuff.

On Tue, 2007-10-23 at 16:10 -0500, Hollis Blanchard wrote:
> On Tue, 2007-10-23 at 15:41 -0500, Jerone Young wrote:
> > 
> > +flatfiles_tests-common = test/bootstrap test/vmexit.flat test/smp.flat
> 
> Instead of "flatfiles_tests-common" (getting a little long, no?), I
> would just call them "tests" and "tests-common" or "tests-x86". We're
> going to have non-flat test binaries in the near future anyways...
> 


-------------------------------------------------------------------------
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/

  reply	other threads:[~2007-10-24  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 20:41 [PATCH 0 of 2] x86 user directory refactoring Jerone Young
2007-10-23 20:41 ` [PATCH 1 of 2] [mq]: x86_user_make_changes Jerone Young
2007-10-23 21:10   ` [kvm-ppc-devel] " Hollis Blanchard
2007-10-24  2:55     ` Jerone Young [this message]
2007-10-23 20:42 ` [PATCH 2 of 2] This patch moves x86 specific tests to there own directory Jerone Young

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=1193194556.5807.0.camel@thinkpad \
    --to=jyoung5-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=hollisb-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