qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
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: Fri, 29 Apr 2011 01:46:45 +0100	[thread overview]
Message-ID: <BANLkTik74F0SzFgyCF5sPp_4eFFE6dPmmA@mail.gmail.com> (raw)
In-Reply-To: <4DB9D2DC.3080201@codemonkey.ws>

On 28 April 2011 21:49, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 04/28/2011 03:02 PM, Stefan Weil wrote:
>> -$(addprefix 9pfs/, $(9pfs-nested-y)): CFLAGS +=  -I$(SRC_PATH)/hw/
>
> Wouldn't it be more straight forward to just do QEMU_CFLAGS +=?

There aren't any other source files in QEMU which have custom
include paths -- why should 9pfs be a special case?

-- PMM

  parent reply	other threads:[~2011-04-29  0:46 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
2011-04-29  0:46             ` Peter Maydell [this message]
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=BANLkTik74F0SzFgyCF5sPp_4eFFE6dPmmA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --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).