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

RE: [Xen-ia64-devel] [PATCH] console

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 3 Nov 2005 05:51:50 -0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 03 Nov 2005 13:49:05 +0000
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
Thread-index: AcXfxDghPdwvKVTiRQyyP/82OPeYGAAYwEYwABU+ZeA=
Thread-topic: [Xen-ia64-devel] [PATCH] console

> A small comment is that bind_virq_to_evtchn is a stale 
> interface none used now. So Dan, you can remove that 
> interface when check-in Tristan's patch.

I don't understand.  Even after Tristan's console.c.patch
patch, there is still a call to bind_virq_to_evtchn.
Or did I misunderstand or misapply the patch?

Dan

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

Follow-Ups:
- Re: [Xen-ia64-devel] [PATCH] console
  - From: Tristan Gingold

Prev by Date: [Xen-ia64-devel] RE: ar.unat[patch] fixed this ar.uant issue.
Next by Date: [Xen-ia64-devel] Re: [PATCH] console
Previous by thread: Re: [Xen-ia64-devel] [PATCH] console
Next by thread: Re: [Xen-ia64-devel] [PATCH] console
Index(es):
- Date
- Thread

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