From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: [Qemu-devel] [PATCH] iov: Move from hw/ to topdir
Date: Tue, 4 May 2010 16:39:07 +0530 [thread overview]
Message-ID: <1272971347-30234-1-git-send-email-amit.shah@redhat.com> (raw)
The iov functions can be useful to other code as well.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
CC: Christoph Hellwig <hch@lst.de>
---
hw/iov.c => iov.c | 0
hw/iov.h => iov.h | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename hw/iov.c => iov.c (100%)
rename hw/iov.h => iov.h (100%)
diff --git a/hw/iov.c b/iov.c
similarity index 100%
rename from hw/iov.c
rename to iov.c
diff --git a/hw/iov.h b/iov.h
similarity index 100%
rename from hw/iov.h
rename to iov.h
--
1.6.2.5
next reply other threads:[~2010-05-04 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 11:09 Amit Shah [this message]
2010-05-10 20:19 ` [Qemu-devel] [PATCH] iov: Move from hw/ to topdir Anthony Liguori
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=1272971347-30234-1-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=hch@lst.de \
--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).