From: Harald Hoyer <harald.hoyer@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kdbus: add documentation
Date: Fri, 21 Nov 2014 09:29:14 +0100 [thread overview]
Message-ID: <546EF7DA.20008@gmail.com> (raw)
In-Reply-To: <1416546149-24799-2-git-send-email-gregkh@linuxfoundation.org>
On 21.11.2014 06:02, Greg Kroah-Hartman wrote:
> From: Daniel Mack <daniel@zonque.org>
> …
> +5.4 Creating buses and endpoints
> +--------------------------------
> +
> +KDBUS_CMD_BUS_MAKE, and KDBUS_CMD_ENDPOINT_MAKE take a
> +struct kdbus_cmd_make argument.
> +
> +struct kdbus_cmd_make {
> + __u64 size;
> + The overall size of the struct, including its items.
> +
> + __u64 flags;
> + The flags for creation.
> +
> + KDBUS_MAKE_ACCESS_GROUP
> + Make the device file group-accessible
device?
> +
> + KDBUS_MAKE_ACCESS_WORLD
> + Make the device file world-accessible
device?
> +
> + __u64 kernel_flags;
> + Valid flags for this command, returned by the kernel upon each call.
> +
> + struct kdbus_item items[0];
> + A list of items, only used for creating custom endpoints. Has specific
> + meanings for KDBUS_CMD_BUS_MAKE and KDBUS_CMD_ENDPOINT_MAKE (see above).
> +};
> …
next prev parent reply other threads:[~2014-11-21 8:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 5:02 [PATCH v2 00/13] Add kdbus implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add documentation Greg Kroah-Hartman
2014-11-21 8:29 ` Harald Hoyer [this message]
2014-11-21 17:12 ` Andy Lutomirski
2014-11-24 20:16 ` David Herrmann
2014-11-24 20:57 ` Andy Lutomirski
2014-11-26 11:55 ` David Herrmann
2014-11-26 15:30 ` Andy Lutomirski
2014-11-26 15:39 ` Andy Lutomirski
2014-11-30 9:08 ` Florian Weimer
2014-11-30 17:12 ` David Herrmann
2014-11-30 17:22 ` Florian Weimer
2014-11-30 8:56 ` Florian Weimer
2014-11-30 17:17 ` David Herrmann
2014-11-30 9:02 ` Florian Weimer
2014-11-30 17:15 ` David Herrmann
2014-11-30 17:23 ` Florian Weimer
2015-01-20 8:09 ` Michael Kerrisk (man-pages)
2015-01-20 8:25 ` Daniel Mack
2015-01-20 12:54 ` Michael Kerrisk (man-pages)
2014-11-21 5:02 ` kdbus: add header file Greg Kroah-Hartman
2014-11-21 8:34 ` Harald Hoyer
2014-11-21 8:55 ` Daniel Mack
2014-11-21 5:02 ` kdbus: add driver skeleton, ioctl entry points and utility functions Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add connection pool implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add connection, queue handling and message validation code Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add node and filesystem implementation Greg Kroah-Hartman
2014-11-21 15:55 ` Sasha Levin
2014-11-21 16:13 ` David Herrmann
2014-11-21 16:56 ` Greg Kroah-Hartman
2014-11-21 17:03 ` Sasha Levin
2014-11-21 17:55 ` Greg Kroah-Hartman
2014-11-21 16:35 ` Andy Lutomirski
2014-11-21 16:41 ` Andy Lutomirski
2014-11-21 16:53 ` David Herrmann
2014-11-21 5:02 ` kdbus: add code to gather metadata Greg Kroah-Hartman
2014-11-21 19:50 ` Andy Lutomirski
2014-12-01 13:50 ` Daniel Mack
2014-12-01 14:46 ` Andy Lutomirski
2014-11-21 5:02 ` kdbus: add code for notifications and matches Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add code for buses, domains and endpoints Greg Kroah-Hartman
2014-11-21 8:14 ` Harald Hoyer
2014-11-21 8:39 ` Harald Hoyer
2014-11-21 5:02 ` kdbus: add name registry implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add policy database implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add Makefile, Kconfig and MAINTAINERS entry Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add selftests Greg Kroah-Hartman
2014-11-21 6:02 ` [PATCH v2 00/13] Add kdbus implementation Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2014-10-29 22:00 [PATCH 00/12] " Greg Kroah-Hartman
2014-10-29 22:00 ` kdbus: add documentation Greg Kroah-Hartman
2014-10-30 12:20 ` Peter Meerwald
2014-11-02 1:29 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=546EF7DA.20008@gmail.com \
--to=harald.hoyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).