Displaying 2 results from an estimated 2 matches for "blkback_id".
Did you mean:
blkback_ids
2008 Mar 05
0
[PATCH] linux: properly qualify all static ''struct xenbus_device_id'' instances
...ead-2008-02-26.orig/drivers/xen/blkback/xenbus.c 2008-03-05 16:30:44.000000000 +0100
+++ head-2008-02-26/drivers/xen/blkback/xenbus.c 2008-03-05 08:58:34.000000000 +0100
@@ -518,7 +518,7 @@ static int connect_ring(struct backend_i
/* ** Driver Registration ** */
-static struct xenbus_device_id blkback_ids[] = {
+static const struct xenbus_device_id blkback_ids[] = {
{ "vbd" },
{ "" }
};
Index: head-2008-02-26/drivers/xen/blkfront/blkfront.c
===================================================================
--- head-2008-02-26.orig/drivers/xen/blkfront/blkfront.c 2008-03-05...
2013 Jul 15
8
[PATCH 0 of 7 v5] Introduce the tapback daemon (most of blkback in user-space)
This patch series introduces the tapback daemon, the user space daemon that
acts as a device''s back-end, essentially most of blkback in user space. The
daemon is responsible for coordinating the front-end and tapdisk. It creates
tapdisk process as needed, instructs them to connect to/disconnect from the
shared ring, and manages the state of the back-end.
The shared ring between the