From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Stezenbach Subject: Re: [PATCH 01/13] kdbus: add documentation Date: Tue, 20 Jan 2015 23:00:28 +0100 Message-ID: <20150120220028.GA13191@sig21.net> References: <1421435777-25306-1-git-send-email-gregkh@linuxfoundation.org> <1421435777-25306-2-git-send-email-gregkh@linuxfoundation.org> <54BE5DC8.70706@gmail.com> <20150120145353.GA8124@dztty> <20150120160842.GA9474@sig21.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: David Herrmann Cc: Djalal Harouni , Josh Boyer , "Michael Kerrisk (man-pages)" , Greg Kroah-Hartman , Arnd Bergmann , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Jiri Kosina , Andy Lutomirski , Linux API , linux-kernel , Daniel Mack List-Id: linux-api@vger.kernel.org Hi David, On Tue, Jan 20, 2015 at 06:00:28PM +0100, David Herrmann wrote: [big snip] > These are just examples off the top of my head, but I think they're > already pretty convincing. Thank you for writing this up. This is the information I was looking for which puts kdbus into context and explains the motivation for its development. Naturally I don't agree with all of it, but I'm content with what I learned so far. Daniel informed me off-list that he (and probably others) does not understand what my questions were aiming at. I'm sorry about that, I thought it was clear I was just lacking the background information to understand what kdbus is and what it is not, and why it exists -- information I couldn't find in some hours of googling. Thanks, Johannes