From: Lyu Mitnick <mitnick.lyu@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] No scratch directory in qemu-iotests
Date: Fri, 8 Apr 2011 09:21:02 +0800 [thread overview]
Message-ID: <BANLkTimxmEbF7MoQZavBHOKhW_-F-YOYfg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hello
When I want to use qemu-iotests, some error occurred:
$ git clone git://
git.kernel.org/pub/scm/linux/kernel/git/hch/qemu-iotests.git
$ cd qemu-iotests
$ ./check -h
common.config: Error: $TEST_DIR
(/home/mitnick/Desktop/GSoC2011/QEMU/qemu-iotests/scratch) is not a
directory
There is no error when I create directory scratch. I am wondering whether
scratch
should be add into qemu-iotests master tree??
Thanks
Mitnick
[-- Attachment #2: Type: text/html, Size: 706 bytes --]
next reply other threads:[~2011-04-08 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 1:21 Lyu Mitnick [this message]
2011-04-08 8:47 ` [Qemu-devel] No scratch directory in qemu-iotests Stefan Hajnoczi
2011-04-11 18:11 ` Christoph Hellwig
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=BANLkTimxmEbF7MoQZavBHOKhW_-F-YOYfg@mail.gmail.com \
--to=mitnick.lyu@gmail.com \
--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).