From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, "Emilio G . Cota" <cota@braap.org>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH] scripts/clean-includes: Mark 'qemu/qemu-plugin.h' as special header
Date: Tue, 26 May 2020 12:24:28 +0100 [thread overview]
Message-ID: <87ftbn6is3.fsf@linaro.org> (raw)
In-Reply-To: <20200524215654.13256-1-f4bug@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> "qemu/qemu-plugin.h" isn't meant to be include by QEMU codebase,
> but by 3rd party plugins that QEMU can use. These plugins can be
> built out of QEMU and don't include "qemu/osdep.h".
> Mark "qemu/qemu-plugin.h" as a special header that doesn't need
> to be cleaned for "qemu/osdep.h".
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> scripts/clean-includes | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/clean-includes b/scripts/clean-includes
> index dd938daa3e..795b3bea31 100755
> --- a/scripts/clean-includes
> +++ b/scripts/clean-includes
> @@ -123,6 +123,7 @@ for f in "$@"; do
> ;;
> *include/qemu/osdep.h | \
> *include/qemu/compiler.h | \
> + *include/qemu/qemu-plugin.h | \
> *include/glib-compat.h | \
> *include/sysemu/os-posix.h | \
> *include/sysemu/os-win32.h | \
Queued to plugins/next, thanks.
--
Alex Bennée
WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-trivial@nongnu.org, "Emilio G . Cota" <cota@braap.org>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] scripts/clean-includes: Mark 'qemu/qemu-plugin.h' as special header
Date: Tue, 26 May 2020 12:24:28 +0100 [thread overview]
Message-ID: <87ftbn6is3.fsf@linaro.org> (raw)
In-Reply-To: <20200524215654.13256-1-f4bug@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> "qemu/qemu-plugin.h" isn't meant to be include by QEMU codebase,
> but by 3rd party plugins that QEMU can use. These plugins can be
> built out of QEMU and don't include "qemu/osdep.h".
> Mark "qemu/qemu-plugin.h" as a special header that doesn't need
> to be cleaned for "qemu/osdep.h".
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> scripts/clean-includes | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/clean-includes b/scripts/clean-includes
> index dd938daa3e..795b3bea31 100755
> --- a/scripts/clean-includes
> +++ b/scripts/clean-includes
> @@ -123,6 +123,7 @@ for f in "$@"; do
> ;;
> *include/qemu/osdep.h | \
> *include/qemu/compiler.h | \
> + *include/qemu/qemu-plugin.h | \
> *include/glib-compat.h | \
> *include/sysemu/os-posix.h | \
> *include/sysemu/os-win32.h | \
Queued to plugins/next, thanks.
--
Alex Bennée
next prev parent reply other threads:[~2020-05-26 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 21:56 [PATCH] scripts/clean-includes: Mark 'qemu/qemu-plugin.h' as special header Philippe Mathieu-Daudé
2020-05-24 21:56 ` Philippe Mathieu-Daudé
2020-05-25 3:05 ` Emilio G. Cota
2020-05-25 3:05 ` Emilio G. Cota
2020-05-26 11:24 ` Alex Bennée [this message]
2020-05-26 11:24 ` Alex Bennée
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=87ftbn6is3.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.