From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
blauwirbel@gmail.com,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3] virtio-9p: Use relative includes for files in hw
Date: Thu, 28 Apr 2011 23:44:53 +0200 [thread overview]
Message-ID: <4DB9DFD5.8000504@mail.berlios.de> (raw)
In-Reply-To: <4DB9D2DC.3080201@codemonkey.ws>
Am 28.04.2011 22:49, schrieb Anthony Liguori:
> On 04/28/2011 03:02 PM, Stefan Weil wrote:
>> Commit 353ac78d495ef976242abd868f68d78420861c2c moved the files
>> without fixing the include paths. It used a modified CFLAGS
>> to add hw to the include search path, but this breaks builds
>> where the user wants to set special CFLAGS. Long include paths
>> also increase compilation time.
>>
>> Therefore this patch removes the special CFLAGS for virtio
>> and fixes the include statements by using relative include paths.
>>
>> v2: Remove special CFLAGS.
>> v3: Update needed for latest QEMU.
>>
>> Signed-off-by: Stefan Weil<weil@mail.berlios.de>
>> ---
>> Makefile.objs | 2 --
>> Makefile.target | 2 --
>> hw/9pfs/virtio-9p-debug.c | 5 +++--
>> hw/9pfs/virtio-9p-local.c | 3 ++-
>> 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.c | 4 ++--
>> 8 files changed, 10 insertions(+), 12 deletions(-)
>>
>> diff --git a/Makefile.objs b/Makefile.objs
>> index 9d8851e..df8cc9c 100644
>> --- a/Makefile.objs
>> +++ b/Makefile.objs
>> @@ -290,8 +290,6 @@ hw-obj-$(CONFIG_SOUND) += $(sound-obj-y)
>> 9pfs-nested-$(CONFIG_VIRTFS) += virtio-9p-xattr-user.o
>> virtio-9p-posix-acl.o
>>
>> hw-obj-$(CONFIG_VIRTFS) += $(addprefix 9pfs/, $(9pfs-nested-y))
>> -$(addprefix 9pfs/, $(9pfs-nested-y)): CFLAGS += -I$(SRC_PATH)/hw/
>
> Wouldn't it be more straight forward to just do QEMU_CFLAGS +=?
>
> Regards,
>
> Anthony Liguori
That would be the second best solution (in my opinion).
Its only advantage would be that it minimises the size of the patch
(which is not a good argument if the result has disadvantages).
Do you think that the lines which I removed in Makefile.* look pretty
and maintainable? I don't think so. The new include statements are
much cleaner. They are also in line with other QEMU code - try
git grep '"hw/'
to see it yourself.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-04-28 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 17:08 [Qemu-devel] [PATCH] virtio-9p: Fix compilation (wrong include statements) Stefan Weil
2011-04-28 17:39 ` Anthony Liguori
2011-04-28 17:44 ` Stefan Weil
2011-04-28 17:46 ` Anthony Liguori
2011-04-28 19:04 ` Blue Swirl
2011-04-28 20:02 ` [Qemu-devel] [PATCH v3] virtio-9p: Use relative includes for files in hw Stefan Weil
2011-04-28 20:49 ` Anthony Liguori
2011-04-28 21:44 ` Stefan Weil [this message]
2011-04-29 0:46 ` Peter Maydell
2011-05-27 18:27 ` Stefan Weil
2011-05-28 16:51 ` Aneesh Kumar K.V
2011-05-28 19:12 ` Venkateswararao Jujjuri
2011-04-28 18:21 ` [Qemu-devel] [PATCH v2] " Stefan Weil
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=4DB9DFD5.8000504@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=aliguori@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.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).