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

Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] x86: Avoid use of domain_crash_synchronous() in C code.


  • To: John Levon <levon@xxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 08 Apr 2008 13:32:40 +0100
  • Delivery-date: Tue, 08 Apr 2008 05:42:53 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciZdKJn4K+vVgVnEd2lZwAX8io7RQ==
  • Thread-topic: [Xen-devel] Re: [Xen-changelog] [xen-unstable] x86: Avoid use of domain_crash_synchronous() in C code.

On 8/4/08 13:30, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> On Tue, Apr 08, 2008 at 02:01:40AM -0700, Xen patchbot-unstable wrote:
> 
>> # HG changeset patch
>> # User Keir Fraser <keir.fraser@xxxxxxxxxx>
>> # Date 1207322752 -3600
>> # Node ID b7637c5269d133fc0828e76814e7f4333729caec
>> # Parent  271ec82db9218b42f5b04c94d41282e145343cc4
>> x86: Avoid use of domain_crash_synchronous() in C code.
> 
> Was this changeset supposed to include all the other IOREQ changes? Just
> checking they didn't get in accidentally?

It was intended. Some of the d_c_s usages fell out when functions were
cleaned up.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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