[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] slightly simplify SCHEDOP_remote_shutdown handling

To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Wed, 17 Jun 2015 13:59:29 +0100
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>
Delivery-date: Wed, 17 Jun 2015 12:59:47 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 17/06/15 13:55, Jan Beulich wrote:
> There's no need for two exit paths each using rcu_unlock_domain() on
> its own here.
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] slightly simplify SCHEDOP_remote_shutdown handling
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] PCI Passthrough ARM Design : Draft1
Next by Date: Re: [Xen-devel] PCI Passthrough ARM Design : Draft1
Previous by thread: [Xen-devel] [PATCH] slightly simplify SCHEDOP_remote_shutdown handling
Next by thread: Re: [Xen-devel] [PATCH] slightly simplify SCHEDOP_remote_shutdown handling
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.