All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	xen-devel@lists.xensource.com,
	Julien Grall <julien.grall@linaro.org>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v2 0/6] interrupt handling fixes
Date: Tue, 10 Dec 2013 18:52:23 +0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1312101851500.7093@kaball.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312101640060.7093@kaball.uk.xensource.com>

On Tue, 10 Dec 2013, Stefano Stabellini wrote:
> On Tue, 10 Dec 2013, Ian Campbell wrote:
> > On Tue, 2013-12-10 at 15:36 +0000, Stefano Stabellini wrote:
> > > On Tue, 10 Dec 2013, Julien Grall wrote:
> > > > On 12/10/2013 03:22 PM, Ian Campbell wrote:
> > > > > On Tue, 2013-12-10 at 13:05 +0000, Stefano Stabellini wrote:
> > > > >> Hi all,
> > > > >> this series is a reworked version of "Fix multiple issues with the
> > > > >> interrupts on ARM":
> > > > > 
> > > > > #1 and #4-#6 are acked they seem comparatively straight forward does it
> > > > > make sense to apply those now without the other two? Is it safe to do
> > > > > so?
> > > > 
> > > > Before applying these patches, I want to give a try on different
> > > > platforms If I'm not mistaken the patch series were only tried on midway.
> > > 
> > > I think I found some bugs. I can wait before testing.
> > 
> > You mean he should wait, right?
> > 
> > I was going to try them as well, but I'll put that on hold for a moment.
> 
> It works well for dom0, but maybe not for domUs. I would wait a bit more
> for tests or apply patches.

The third version of the series works well for me for dom0 and domUs. I
would encourage you to test it.

  reply	other threads:[~2013-12-10 18:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 13:05 [PATCH v2 0/6] interrupt handling fixes Stefano Stabellini
2013-12-10 13:06 ` [PATCH v2 1/6] xen/arm: Physical IRQ is not always equal to virtual IRQ Stefano Stabellini
2013-12-10 13:06 ` [PATCH v2 2/6] xen/arm: track the state of guest IRQs Stefano Stabellini
2013-12-10 13:06 ` [PATCH v2 3/6] xen/arm: do not add a second irq to the LRs if one is already present Stefano Stabellini
2013-12-10 15:22   ` Ian Campbell
2013-12-10 13:06 ` [PATCH v2 4/6] xen/arm: implement gic_irq_enable and gic_irq_disable Stefano Stabellini
2013-12-10 13:06 ` [PATCH v2 5/6] xen/arm: Only enable physical IRQs when the guest asks Stefano Stabellini
2013-12-10 15:18   ` Ian Campbell
2013-12-10 13:06 ` [PATCH v2 6/6] xen/arm: disable a physical IRQ when the guest disables the corresponding IRQ Stefano Stabellini
2013-12-10 15:20   ` Ian Campbell
2013-12-10 18:36     ` Stefano Stabellini
2013-12-11 10:28       ` Ian Campbell
2013-12-11 19:01         ` Stefano Stabellini
2013-12-12 10:21           ` Ian Campbell
2013-12-10 15:22 ` [PATCH v2 0/6] interrupt handling fixes Ian Campbell
2013-12-10 15:30   ` Julien Grall
2013-12-10 15:36     ` Stefano Stabellini
2013-12-10 16:06       ` Ian Campbell
2013-12-10 16:46         ` Stefano Stabellini
2013-12-10 18:52           ` Stefano Stabellini [this message]
2013-12-10 18:34   ` Stefano Stabellini

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=alpine.DEB.2.02.1312101851500.7093@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=julien.grall@linaro.org \
    --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.