From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>,
xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v2 0/3] libxl: fd events: Recheck with poll
Date: Fri, 17 Apr 2015 16:25:32 -0400 [thread overview]
Message-ID: <20150417202532.GA15171@l.oracle.com> (raw)
In-Reply-To: <21807.65132.818784.976356@mariner.uk.xensource.com>
On Thu, Apr 16, 2015 at 07:24:44PM +0100, Ian Jackson wrote:
> Ian Jackson writes
> ("<21807.61130.841852.546321@mariner.uk.xensource.com>"):
>
> Gah, mangled the subject line.
I've tested those three patches and they work fine. To make sure that
they did fix the problem I went back to Xen before these patches
to make sure I can reproduce the failure .. and of course I can't.
I am going to try next week to reproduce the error case
to make sure it does fix the issue.
>
> Ian.
next prev parent reply other threads:[~2015-04-17 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH v2 0/3] libxl: fd events: Recheck fd events>
2015-04-16 18:23 ` <21807.61130.841852.546321@mariner.uk.xensource.com> Ian Jackson
2015-04-16 18:23 ` [PATCH 1/3] libxl: fd events: Break out libxl__fd_poll_recheck Ian Jackson
2015-04-17 9:01 ` Ian Campbell
2015-04-16 18:23 ` [PATCH 2/3] libxl: fd events: Break out fd_occurs Ian Jackson
2015-04-17 9:02 ` Ian Campbell
2015-04-17 20:21 ` Konrad Rzeszutek Wilk
2015-04-16 18:23 ` [PATCH 3/3] libxl: fd events: Suppress spurious fd events Ian Jackson
2015-04-17 9:17 ` Ian Campbell
2015-04-16 18:24 ` [PATCH v2 0/3] libxl: fd events: Recheck with poll Ian Jackson
2015-04-17 20:25 ` Konrad Rzeszutek Wilk [this message]
2015-04-22 14:23 ` Ian Campbell
2015-04-16 21:19 ` Jim Fehlig
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=20150417202532.GA15171@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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 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.