From: Peter Maydell <peter.maydell@linaro.org>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 07/22] linux-user: Use absolute include path
Date: Tue, 26 Mar 2013 14:06:26 +0000 [thread overview]
Message-ID: <CAFEAcA8cH+0raM+aChbkZ8mcvO_XS4rjGxpFkV4+xeaKnLeqWQ@mail.gmail.com> (raw)
In-Reply-To: <20130326140100.4471.33758.stgit@fimbulvetr.bsc.es>
On 26 March 2013 14:01, Lluís Vilanova <vilanova@ac.upc.edu> wrote:
> Lets the include directive work regardless of the current directory.
>
> This is needed for code compiled in directories deeper than one level from the
> build root.
Something odd here -- linux-headers/ is not for
linux-user mode, it's only needed for system mode (and
specifically for KVM support). Possibly just an error
in the commit message? I think the code change looks OK.
-- PMM
next prev parent reply other threads:[~2013-03-26 14:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:00 [Qemu-devel] [RFC][PATCH 00/22] instrument: Let the user wrap/override specific event tracing routines Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 01/22] instrument: Add documentation Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 02/22] trace: [simple] Do not include "trace/simple.h" in generated tracer headers Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 03/22] trace: Let the user specify her own trace-events file Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 04/22] tracetool: Use method 'Event.api' to get the name of public routines Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 05/22] trace: Minimize inclusions of "qemu-common.h" to avoid inclusion loops Lluís Vilanova
2013-03-26 14:00 ` [Qemu-devel] [PATCH 06/22] instrument: [none] Add null instrumentation Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 07/22] linux-user: Use absolute include path Lluís Vilanova
2013-03-26 14:06 ` Peter Maydell [this message]
2013-03-26 15:15 ` Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 08/22] instrument: [static] Call statically linked user-provided routines Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 09/22] instrument: [dynamic] Call dynamically " Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 10/22] instrument: Add internal control interface Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 11/22] instrument: [hmp] Add " Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 12/22] qapi: Add a primitive to include other files from a QAPI schema file Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 13/22] [trivial] Set the input root directory when parsing QAPI files Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 14/22] instrument: [qmp, qapi] Add control interface Lluís Vilanova
2013-03-26 14:52 ` Eric Blake
2013-03-26 15:39 ` Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 15/22] Let makefiles add entries to the set of target architecture objects Lluís Vilanova
2013-03-26 14:01 ` [Qemu-devel] [PATCH 16/22] instrument: Add commandline options to start with an instrumentation library Lluís Vilanova
2013-03-26 14:59 ` Eric Blake
2013-03-26 14:01 ` [Qemu-devel] [PATCH 17/22] instrument: Add client-side API to enumerate events Lluís Vilanova
2013-03-26 14:02 ` [Qemu-devel] [PATCH 18/22] instrument: Add client-side API to control tracing state of events Lluís Vilanova
2013-03-26 14:02 ` [Qemu-devel] [PATCH 19/22] instrument: Add client-side API to control event instrumentation Lluís Vilanova
2013-03-26 14:02 ` [Qemu-devel] [PATCH 20/22] build: Fix installation of target-dependant files Lluís Vilanova
2013-03-26 14:02 ` [Qemu-devel] [PATCH 21/22] instrument: Install headers for dynamic instrumentation clients Lluís Vilanova
2013-03-26 14:02 ` [Qemu-devel] [PATCH 22/22] trace: Do not use the word 'new' in event arguments Lluís Vilanova
2013-04-11 9:07 ` [Qemu-devel] [RFC][PATCH 00/22] instrument: Let the user wrap/override specific event tracing routines Stefan Hajnoczi
2013-04-11 12:29 ` Lluís Vilanova
2013-04-12 8:18 ` Stefan Hajnoczi
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=CAFEAcA8cH+0raM+aChbkZ8mcvO_XS4rjGxpFkV4+xeaKnLeqWQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).