From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-9p: move 9p files around
Date: Wed, 27 Apr 2011 22:01:51 +0530 [thread overview]
Message-ID: <87tydjwt8o.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <4DB83CFC.4000800@linux.vnet.ibm.com>
On Wed, 27 Apr 2011 08:57:48 -0700, Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com> wrote:
> On 04/27/2011 03:33 AM, Aneesh Kumar K.V wrote:
> > On Wed, 27 Apr 2011 09:03:56 +0200, Jan Kiszka<jan.kiszka@web.de> wrote:
> >> On 2011-04-27 08:53, Aneesh Kumar K.V wrote:
> >>> Now that we start adding more files related to 9pfs
> >>> it make sense to move them to a separate directory
> >>>
> >>> Signed-off-by: Aneesh Kumar K.V<aneesh.kumar@linux.vnet.ibm.com>
> >>> ---
> >>> Makefile.objs | 10 +++++++---
> >>> Makefile.target | 6 ++++--
> >>> configure | 2 ++
> >>> {hw => fsdev}/file-op-9p.h | 0
> >>> fsdev/qemu-fsdev.h | 2 +-
> >>> hw/{ => 9pfs}/virtio-9p-debug.c | 0
> >>> hw/{ => 9pfs}/virtio-9p-debug.h | 0
> >>> hw/{ => 9pfs}/virtio-9p-local.c | 0
> >>> hw/{ => 9pfs}/virtio-9p-posix-acl.c | 2 +-
> >>> hw/{ => 9pfs}/virtio-9p-xattr-user.c | 2 +-
> >>> hw/{ => 9pfs}/virtio-9p-xattr.c | 2 +-
> >>> hw/{ => 9pfs}/virtio-9p-xattr.h | 0
> >>> hw/{ => 9pfs}/virtio-9p.c | 0
> >>> hw/{ => 9pfs}/virtio-9p.h | 2 +-
> >>> 14 files changed, 18 insertions(+), 10 deletions(-)
> >>> rename {hw => fsdev}/file-op-9p.h (100%)
> >>> rename hw/{ => 9pfs}/virtio-9p-debug.c (100%)
> >>> rename hw/{ => 9pfs}/virtio-9p-debug.h (100%)
> >>> rename hw/{ => 9pfs}/virtio-9p-local.c (100%)
> >>> rename hw/{ => 9pfs}/virtio-9p-posix-acl.c (99%)
> >>> rename hw/{ => 9pfs}/virtio-9p-xattr-user.c (98%)
> >>> rename hw/{ => 9pfs}/virtio-9p-xattr.c (99%)
> >>> rename hw/{ => 9pfs}/virtio-9p-xattr.h (100%)
> >>> rename hw/{ => 9pfs}/virtio-9p.c (100%)
> >> That's a good chance to split up this file, move virtio_9p_get_config
> >> into a separate one and build the large virtio-9p.c as part of hwlib
> >> while keeping the new file target-specific. I've some hack for this
> >> lying around, but now that you are already at it...
> >>
> > How about doing the below patch also and move all those device specific
> > stuff to virtio-9p-device.c and rest in virtio-9p.c ?
> I think this goes on top of your old patch. I am ready to give pull to
> Anthony with old patch.
> May be this can go in next pull?
>
Yes the two new patches can go later
-aneesh
next prev parent reply other threads:[~2011-04-27 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 6:53 [Qemu-devel] [PATCH] virtio-9p: move 9p files around Aneesh Kumar K.V
2011-04-27 7:03 ` Jan Kiszka
2011-04-27 10:33 ` Aneesh Kumar K.V
2011-04-27 14:55 ` Jan Kiszka
2011-04-27 15:57 ` Venkateswararao Jujjuri
2011-04-27 16:31 ` Aneesh Kumar K.V [this message]
2011-04-27 11:46 ` [Qemu-devel] [PATCH 1/3] virtio-9p: Move 9p device registration into virtio-9p.c Aneesh Kumar K.V
2011-04-27 11:46 ` [Qemu-devel] [PATCH 2/3] virtio-9p: move 9p files around Aneesh Kumar K.V
2011-04-27 11:46 ` [Qemu-devel] [PATCH 3/3] virtio-9p: Move device specific code to virtio-9p-device Aneesh Kumar K.V
2011-05-31 21:28 ` [Qemu-devel] [PATCH 1/3] virtio-9p: Move 9p device registration into virtio-9p.c Venkateswararao Jujjuri
2011-06-01 6:49 ` Aneesh Kumar K.V
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=87tydjwt8o.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=jvrao@linux.vnet.ibm.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).