From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Bug xen/next.. WARNING: at /home/konrad/git/nex-VI-PVOPS/linux/kernel/irq/manage.c:274 __enable_irq+0x5c/0xaf(
Date: Tue, 09 Mar 2010 15:24:09 -0800 [thread overview]
Message-ID: <4B96D899.4050800@goop.org> (raw)
In-Reply-To: <20100309155234.GC22018@phenom.dumpdata.com>
On 03/09/2010 07:52 AM, Konrad Rzeszutek Wilk wrote:
> Jeremy,
>
> This one looks quite familiar. I think I pointed this one out to you the
> first time I started working on pv-ops (so, June/July?) and you had a
> fix for it, but I can't remember the details (except that you did ask me
> to review it, and I did, but I didn't send any details back).
>
Ah, yeah, something wrong with the /dev/evtchn driver. Ah, I forgot to
merge in xen/dev-evtchn into xen/next; try that and see what happens.
(I'll test it too, but it may have to wait for tomorrow.)
J
prev parent reply other threads:[~2010-03-09 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 15:52 Bug xen/next.. WARNING: at /home/konrad/git/nex-VI-PVOPS/linux/kernel/irq/manage.c:274 __enable_irq+0x5c/0xaf( Konrad Rzeszutek Wilk
2010-03-09 23:24 ` Jeremy Fitzhardinge [this message]
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=4B96D899.4050800@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.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.