From: Anthony PERARD <anthony.perard@citrix.com>
To: <qemu-devel@nongnu.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org,
Paul Durrant <paul.durrant@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [Xen-devel] [PATCH v2 0/4] Fix build of Xen support + cleanup
Date: Tue, 18 Jun 2019 12:23:37 +0100 [thread overview]
Message-ID: <20190618112341.513-1-anthony.perard@citrix.com> (raw)
Hi,
Fix the build in osstest and some cleanup
For reference:
Recent flight failure:
https://lists.xenproject.org/archives/html/xen-devel/2019-06/msg01022.html
Bisect result:
https://lists.xenproject.org/archives/html/xen-devel/2019-06/msg01029.html
Thanks.
Anthony PERARD (4):
xen: Fix build with public headers
xen: Import other xen/io/*.h
xen: Drop includes of xen/hvm/params.h
xen: Avoid VLA
hw/9pfs/xen-9pfs.h | 4 +-
hw/block/xen_blkif.h | 5 +-
hw/char/xen_console.c | 2 +-
hw/display/xenfb.c | 7 +-
hw/i386/xen/xen-hvm.c | 16 +-
hw/i386/xen/xen-mapcache.c | 2 -
hw/net/xen_nic.c | 2 +-
hw/usb/xen-usb.c | 3 +-
hw/xen/xen-legacy-backend.c | 2 -
include/hw/xen/interface/grant_table.h | 36 +
include/hw/xen/interface/io/blkif.h | 712 +++++++++++++++
include/hw/xen/interface/io/console.h | 46 +
include/hw/xen/interface/io/fbif.h | 156 ++++
include/hw/xen/interface/io/kbdif.h | 566 ++++++++++++
include/hw/xen/interface/io/netif.h | 1010 ++++++++++++++++++++++
include/hw/xen/interface/io/protocols.h | 42 +
include/hw/xen/{ => interface}/io/ring.h | 0
include/hw/xen/interface/io/usbif.h | 254 ++++++
include/hw/xen/interface/io/xenbus.h | 70 ++
include/hw/xen/xen_common.h | 2 +-
20 files changed, 2914 insertions(+), 23 deletions(-)
create mode 100644 include/hw/xen/interface/grant_table.h
create mode 100644 include/hw/xen/interface/io/blkif.h
create mode 100644 include/hw/xen/interface/io/console.h
create mode 100644 include/hw/xen/interface/io/fbif.h
create mode 100644 include/hw/xen/interface/io/kbdif.h
create mode 100644 include/hw/xen/interface/io/netif.h
create mode 100644 include/hw/xen/interface/io/protocols.h
rename include/hw/xen/{ => interface}/io/ring.h (100%)
create mode 100644 include/hw/xen/interface/io/usbif.h
create mode 100644 include/hw/xen/interface/io/xenbus.h
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-06-18 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:23 Anthony PERARD [this message]
2019-06-18 11:23 ` [Xen-devel] [PATCH v2 1/4] xen: Fix build with public headers Anthony PERARD
2019-06-18 12:14 ` [Xen-devel] [Qemu-devel] " Daniel P. Berrangé
2019-06-20 14:44 ` Anthony PERARD
2019-06-18 11:23 ` [Xen-devel] [PATCH v2 2/4] xen: Import other xen/io/*.h Anthony PERARD
2019-06-18 11:23 ` [Xen-devel] [PATCH v2 3/4] xen: Drop includes of xen/hvm/params.h Anthony PERARD
2019-06-18 11:51 ` Paul Durrant
2019-06-18 11:23 ` [Xen-devel] [PATCH v2 4/4] xen: Avoid VLA Anthony PERARD
2019-06-18 11:35 ` [Xen-devel] [Qemu-devel] " Philippe Mathieu-Daudé
2019-06-18 11:52 ` [Xen-devel] " Paul Durrant
2019-06-18 12:00 ` [Xen-devel] [PATCH v2 0/4] Fix build of Xen support + cleanup no-reply
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=20190618112341.513-1-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).