[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150120220028.GA13191@sig21.net>
Date: Tue, 20 Jan 2015 23:00:28 +0100
From: Johannes Stezenbach <js@...21.net>
To: David Herrmann <dh.herrmann@...il.com>
Cc: Djalal Harouni <tixxdz@...ndz.org>,
Josh Boyer <jwboyer@...oraproject.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
Andy Lutomirski <luto@...capital.net>,
Linux API <linux-api@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Daniel Mack <daniel@...que.org>
Subject: Re: [PATCH 01/13] kdbus: add documentation
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists