From: Grant Likely <grant.likely@secretlab.ca>
To: Tony Ibbs <tibs@tonyibbs.co.uk>
Cc: Linux-embedded <linux-embedded@vger.kernel.org>,
Tibs at Kynesim <tibs@kynesim.co.uk>,
Richard Watts <rrw@kynesim.co.uk>
Subject: Re: [PATCH 0/5] RFC: KBUS messaging subsystem
Date: Mon, 28 Feb 2011 00:52:33 -0700 [thread overview]
Message-ID: <AANLkTim8w4LKjGSekq6jNvvdeBrUYTUMFgCVeduPxiod@mail.gmail.com> (raw)
In-Reply-To: <20110228074859.GE7855@angua.secretlab.ca>
On Mon, Feb 28, 2011 at 12:48 AM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> On Sun, Feb 27, 2011 at 06:11:43PM +0000, Tony Ibbs wrote:
>> KBUS is a lightweight, Linux kernel mediated, message system,
>> particularly intended for use in embedded environments.
>>
>> It is meant to be simple to use and understand. It is designed to
>> provide predictable message delivery, deterministic message ordering,
>> and a guaranteed reply for each request.
>>
>> It is especially aimed at situations where existing solutions,
>> such as DBUS, cannot be used, typically because of system constraints.
>>
>> We have various customers using KBUS in real life, and believe it to
>> be useful. I had a showcase table for KBUS at the ELCE in Cambridge,
>> October last year, and there seemed to be interest.
>>
>> I am hoping to get a response from this list before attempting to send
>> to the kernel list, since I believe this list should contain people
>> who might be most interested in using it.
>
> Just go ahead and post to lkml. There isn't a whole lot of point in
> holding back from there, and that is the only way you'll get the level
> of review that you need to even be considered for merging.
In fact, I think I'll hold off on reviewing this series until lkml is
cc'd so that I don't end up repeating myself. :-)
g.
next prev parent reply other threads:[~2011-02-28 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 18:11 [PATCH 0/5] RFC: KBUS messaging subsystem Tony Ibbs
2011-02-27 18:11 ` [PATCH 1/5] Documentation for KBUS Tony Ibbs
2011-02-27 18:11 ` [PATCH 2/5] External header file " Tony Ibbs
2011-02-27 18:11 ` [PATCH 3/5] Kconfig files and Makefile " Tony Ibbs
2011-02-27 18:11 ` [PATCH 4/5] Internal header file " Tony Ibbs
2011-02-27 18:19 ` [PATCH 3/5] Kconfig files and Makefile " Randy Dunlap
2011-02-27 19:36 ` Tony Ibbs
2011-02-27 19:26 ` [PATCH 5/5] KBUS source file Tony Ibbs
2011-02-27 20:25 ` Randy Dunlap
2011-02-28 19:23 ` Sam Ravnborg
2011-02-28 22:25 ` Tony Ibbs
2011-03-01 5:42 ` Sam Ravnborg
2011-02-28 7:48 ` [PATCH 0/5] RFC: KBUS messaging subsystem Grant Likely
2011-02-28 7:52 ` Grant Likely [this message]
2011-02-28 19:13 ` Tony Ibbs
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=AANLkTim8w4LKjGSekq6jNvvdeBrUYTUMFgCVeduPxiod@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linux-embedded@vger.kernel.org \
--cc=rrw@kynesim.co.uk \
--cc=tibs@kynesim.co.uk \
--cc=tibs@tonyibbs.co.uk \
/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).