qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: <qemu-devel@nongnu.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel@lists.xenproject.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 6/8] xen: Drop includes of xen/hvm/params.h
Date: Mon, 24 Jun 2019 16:32:55 +0100	[thread overview]
Message-ID: <20190624153257.20163-7-anthony.perard@citrix.com> (raw)
In-Reply-To: <20190624153257.20163-1-anthony.perard@citrix.com>

xen-mapcache.c doesn't needs params.h.

xen-hvm.c uses defines available in params.h but so is xen_common.h
which is included before. HVM_PARAM_* flags are only needed to make
xc_hvm_param_{get,set} calls so including only xenctrl.h, which is
where the definition the function is, should be enough.
(xenctrl.h does include params.h)

Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
Message-Id: <20190618112341.513-4-anthony.perard@citrix.com>
---
 hw/i386/xen/xen-hvm.c      | 1 -
 hw/i386/xen/xen-mapcache.c | 2 --
 2 files changed, 3 deletions(-)

diff --git a/hw/i386/xen/xen-hvm.c b/hw/i386/xen/xen-hvm.c
index ed9c37c72d..469f1260a4 100644
--- a/hw/i386/xen/xen-hvm.c
+++ b/hw/i386/xen/xen-hvm.c
@@ -27,7 +27,6 @@
 #include "exec/address-spaces.h"
 
 #include <xen/hvm/ioreq.h>
-#include <xen/hvm/params.h>
 #include <xen/hvm/e820.h>
 
 //#define DEBUG_XEN_HVM
diff --git a/hw/i386/xen/xen-mapcache.c b/hw/i386/xen/xen-mapcache.c
index 254759f776..dc73c86c61 100644
--- a/hw/i386/xen/xen-mapcache.c
+++ b/hw/i386/xen/xen-mapcache.c
@@ -17,8 +17,6 @@
 #include "hw/xen/xen-legacy-backend.h"
 #include "qemu/bitmap.h"
 
-#include <xen/hvm/params.h>
-
 #include "sysemu/xen-mapcache.h"
 #include "trace.h"
 
-- 
Anthony PERARD



  parent reply	other threads:[~2019-06-24 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 15:32 [Qemu-devel] [PULL 0/8] xen queue 2019-06-24 Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 1/8] xen-block: support feature-large-sector-size Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 2/8] xen-bus: use a separate fd for each event channel Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 3/8] xen-bus: allow AioContext to be specified " Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 4/8] xen-bus / xen-block: add support for event channel polling Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 5/8] xen: Avoid VLA Anthony PERARD
2019-06-24 15:32 ` Anthony PERARD [this message]
2019-06-24 15:32 ` [Qemu-devel] [PULL 7/8] Revert xen/io/ring.h of "Clean up a few header guard symbols" Anthony PERARD
2019-06-24 15:32 ` [Qemu-devel] [PULL 8/8] xen: Import other xen/io/*.h Anthony PERARD
2019-06-24 16:10 ` [Qemu-devel] [Xen-devel] [PULL 0/8] xen queue 2019-06-24 no-reply
2019-06-24 16:28 ` no-reply
2019-06-24 16:34 ` no-reply
2019-06-24 16:48 ` no-reply
2019-06-24 17:19 ` no-reply
2019-07-01 12:45 ` [Qemu-devel] " Peter Maydell

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=20190624153257.20163-7-anthony.perard@citrix.com \
    --to=anthony.perard@citrix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xenproject.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).