qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: nick@bytemark.co.uk
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] tests: allow qemu-iotests to be run against nbd backend
Date: Fri, 02 Nov 2012 13:41:35 +0100	[thread overview]
Message-ID: <5093BF7F.8090203@redhat.com> (raw)
In-Reply-To: <1351852086-26789-1-git-send-email-nick@bytemark.co.uk>

Il 02/11/2012 11:28, nick@bytemark.co.uk ha scritto:
> @@ -197,12 +198,14 @@ testlist options
>  	    IMGPROTO=rbd
>  	    xpand=false
>  	    ;;
> -
>  	-sheepdog)
>  	    IMGPROTO=sheepdog
>  	    xpand=false
>  	    ;;
> -
> +    -nbd)
> +        IMGPROTO=nbd
> +        xpand=false
> +        ;;
>  	-nocache)

Spacing problem?

Paolo

  reply	other threads:[~2012-11-02 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 10:28 [Qemu-devel] [PATCH v2] tests: allow qemu-iotests to be run against nbd backend nick
2012-11-02 12:41 ` Paolo Bonzini [this message]
2012-11-02 13:01   ` Nicholas Thomas
2012-11-02 13:19   ` Kevin Wolf

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=5093BF7F.8090203@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=nick@bytemark.co.uk \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).