On 21.11.2014 06:02, Greg Kroah-Hartman wrote:
> From: Daniel Mack <dan...@zonque.org>
> …
> +
> +/**
> + * enum kdbus_make_flags - Flags for KDBUS_CMD_{BUS,EP,NS}_MAKE
> + * @KDBUS_MAKE_ACCESS_GROUP: Make the device node group-accessible
> + * @KDBUS_MAKE_ACCESS_WORLD: Make the device node world-accessible
> + */
> +enum kdbus_make_flags {
> + KDBUS_MAKE_ACCESS_GROUP = 1ULL << 0,
> + KDBUS_MAKE_ACCESS_WORLD = 1ULL << 1,
> +};
> +
"device node"
…
> +/**
> + * Ioctl API
> + * KDBUS_CMD_BUS_MAKE: After opening the "control" device
> node, this
> + * command creates a new bus with the specified
> + * name. The bus is immediately shut down and
> + * cleaned up when the opened "control" device node
> + * is closed.
"device node"
> + * KDBUS_CMD_ENDPOINT_MAKE: Creates a new named special endpoint to talk to
> + * the bus. Such endpoints usually carry a more
> + * restrictive policy and grant restricted access
> + * to specific applications.
> + * KDBUS_CMD_HELLO: By opening the bus device node a connection is
> + * created. After a HELLO the opened connection
> + * becomes an active peer on the bus.
"device node"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
