 Home |
Products |
Support |
Community |
News |
xen-devel
[XenPPC] /dev/mem and xlate_dev_mem_ptr*()
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [XenPPC] /dev/mem and xlate_dev_mem_ptr*() |
| From: | Jimi Xenidis <jimix@xxxxxxxxxxxxxx> |
| Date: | Sat, 27 Jan 2007 07:49:01 -0500 |
| Cc: | xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Sat, 27 Jan 2007 04:48:35 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen PPC development <xen-ppc-devel.lists.xensource.com> |
| List-post: | <mailto:xen-ppc-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx |
in the 2.6.18 linux of the sparse tree you have: drivers/xen/char/mem.c using xlate_dev_mem_ptr as 2 args. What is the story with this? has the interface changed from under you?Why not invent a new interface that does not conflict, since this is your code? -JX _______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ppc-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] backend and frontend, tgh |
|---|---|
| Next by Date: | Re: [Xen-devel] /dev/mem and xlate_dev_mem_ptr*(), Keir Fraser |
| Previous by Thread: | [Xen-devel] Fw: regarding SHM2 mode in xen, jeet |
| Next by Thread: | Re: [Xen-devel] /dev/mem and xlate_dev_mem_ptr*(), Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
