From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Jim Fehlig <jfehlig@suse.com>, Ian Campbell <Ian.Campbell@citrix.com>
Subject: [PATCH 0/2 v4.1] libxl: fix event races exposed by libvirt
Date: Wed, 23 Jan 2013 18:21:19 +0000 [thread overview]
Message-ID: <1358965281-23755-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
This is the really honestly final version of these patches which are
needed to make Jim Fehlig's libvirt libxl driver work.
1/2 libxl: fix stale fd event callback race
2/2 libxl: fix stale timeout event callback race
It appears that I didn't run git-format-patch before git-send-email
when I sent out v4, so they are missing an important bugfix from Jim
Fehlig. Sorry about that.
Ian.
next reply other threads:[~2013-01-23 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 18:21 Ian Jackson [this message]
2013-01-23 18:21 ` [PATCH 1/2] libxl: fix stale fd event callback race Ian Jackson
2013-01-23 18:21 ` [PATCH 2/2] libxl: fix stale timeout " Ian Jackson
2013-01-23 19:08 ` [PATCH 0/2 v4.1] libxl: fix event races exposed by libvirt Jim Fehlig
2013-01-24 10:21 ` Ian Campbell
2013-01-24 13:01 ` Ian Campbell
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=1358965281-23755-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=jfehlig@suse.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).