From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Steven Haigh <netwiz@crc.id.au>, Jan Beulich <JBeulich@suse.com>,
Ian Jackson <ian.jackson@citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: [Xen-devel] [PATCH for-4.13 0/2] xen: Build fixes related to Python3
Date: Sat, 7 Dec 2019 16:52:50 +0000 [thread overview]
Message-ID: <20191207165252.1045-1-andrew.cooper3@citrix.com> (raw)
Patch 2 is a fix for a problem reported on IRC. It is a very-nice-to-have
considering our attempt to make Xen 4.13 Py3-clean.
While testing patch 2, it became apparent that XSM/Flask isn't Py3-clean, and
this is a blocker. It is addressed in patch 1.
Andrew Cooper (2):
xen/flask: Fix Python 3 problems with gen-policy.py
xen/build: Automatically locate a suitable python interpreter
xen/Makefile | 2 ++
xen/xsm/flask/Makefile | 6 ++----
xen/xsm/flask/flask-policy.S | 20 ++++++++++++++++++++
xen/xsm/flask/gen-policy.py | 23 -----------------------
4 files changed, 24 insertions(+), 27 deletions(-)
create mode 100644 xen/xsm/flask/flask-policy.S
delete mode 100644 xen/xsm/flask/gen-policy.py
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-12-07 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 16:52 Andrew Cooper [this message]
2019-12-07 16:52 ` [Xen-devel] [PATCH 1/2] xen/flask: Fix Python 3 problems with gen-policy.py Andrew Cooper
2019-12-07 16:52 ` [Xen-devel] [PATCH 2/2] xen/build: Automatically locate a suitable python interpreter Andrew Cooper
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=20191207165252.1045-1-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@citrix.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=netwiz@crc.id.au \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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 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.