All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/2] xen: allow on_selected_cpus with interrupts disabled
Date: Fri, 03 May 2013 18:38:16 +0100	[thread overview]
Message-ID: <CDA9B498.240C1%keir.xen@gmail.com> (raw)
In-Reply-To: <1367597058.28742.126.camel@zakaz.uk.xensource.com>

On 03/05/2013 17:04, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:

> On Fri, 2013-05-03 at 17:01 +0100, Ian Campbell wrote:
>> On Fri, 2013-05-03 at 16:57 +0100, Keir Fraser wrote:
> 
>>> There's little chance of me being flexible on changing the
>>> on_selected_cpus() interface.
>> 
>> I hadn't noticed this was common code, but in any case I agree with you.
> 
> Which reminds me  -- any chance you could Ack/Nack Julien's patch which
> moves the original code (i.e. without this change) to common code.
> 
> "[PATCH V2 2/2] xen/arm: implement smp_call_function"
> <1366119508-9227-3-git-send-email-julien.grall@citrix.com>

Okay, I will take a look. :)

> Ian.
> 

  reply	other threads:[~2013-05-03 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 14:58 [PATCH 0/2] xen: EOI on the correct GICC interface Stefano Stabellini
2013-05-03 14:58 ` [PATCH 1/2] xen: allow on_selected_cpus with interrupts disabled Stefano Stabellini
2013-05-03 15:21   ` Ian Campbell
2013-05-03 15:57     ` Keir Fraser
2013-05-03 16:01       ` Ian Campbell
2013-05-03 16:04         ` Ian Campbell
2013-05-03 17:38           ` Keir Fraser [this message]
2013-05-03 16:40     ` Stefano Stabellini
2013-05-03 15:53   ` Keir Fraser
2013-05-03 14:58 ` [PATCH 2/2] xen/gic: EOI irqs on the right pcpu Stefano Stabellini
2013-05-03 15:13   ` Julien Grall

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=CDA9B498.240C1%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=julien.grall@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 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.