From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: [PATCH for-4.7 0/3] XSA-175/XSA-178 followups
Date: Thu, 2 Jun 2016 16:10:29 +0100 [thread overview]
Message-ID: <1464880232-893-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
These three patches came out of my development of the XSA-175/XSA-178
fixes.
The rest of the XSA-175/XSA-178 patches, as sent out in the advisory,
have just been applied to staging. These three patches have not, yet.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-02 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:10 Ian Jackson [this message]
2016-06-02 15:10 ` [PATCH 1/3] libxl: Cleanup: Have libxl__alloc_vdev use /libxl Ian Jackson
2016-06-02 15:10 ` [PATCH 2/3] libxl: Cleanup: use libxl__backendpath_parse_domid in libxl__device_disk_from_xs_be Ian Jackson
2016-06-02 15:10 ` [PATCH 3/3] libxl: Document ~/serial/ correctly Ian Jackson
2016-06-02 15:14 ` [PATCH for-4.7 0/3] XSA-175/XSA-178 followups Wei Liu
2016-06-02 15:36 ` Wei Liu
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=1464880232-893-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).