From: Grant Likely <grant.likely@secretlab.ca>
To: Tony Ibbs <tibs@kynesim.co.uk>
Cc: linux-embedded@vger.kernel.org, tibs@tonyibbs.co.uk, rrw@kynesim.co.uk
Subject: Re: [RFC][PATCH] KBUS messaging subsystem
Date: Tue, 1 Feb 2011 20:40:08 -0700 [thread overview]
Message-ID: <20110202034008.GC29148@angua.secretlab.ca> (raw)
In-Reply-To: <20110128180158.6f670a51@spoon>
On Fri, Jan 28, 2011 at 06:01:58PM +0000, Tony Ibbs wrote:
> We talked briefly at ELCE 2010 in Cambridge, after the "keeping
> kernel maintainers happy" talk, and you offered that I could
> CC you when I got round to submitting our kernel module.
Hi Tony,
Yes, I remember talking to you. I'll take a look through and see if I
see any glaring problems. However, my major critique still stands.
There are already a large number of communication channels available
to Linux, with DBUS gatting the most attention at the moment. What
niche is KBUS filling that DBUS and others misses? Secondarily, does
KBUS implement a new API instead of extending an existing mechanism to
meet your needs? I suspect you'll get a lot more traction if KBUS can
make DBUS work better/faster/more efficiently.
> I've just emailed the embedded linux mailing list with an initial
> question about it, and attempted to CC you as
> grant.likely@secretlab.com, which appears to have bounced. I'm
> hoping that I just wrote the address down wrong, and the .ca
> version is correct.
Yes, the correct domain is secretlab.ca
>
> Apologies for any confusion,
> Tibs
>
> Begin forwarded message:
>
> Date: Fri, 28 Jan 2011 17:50:40 +0000
> From: Tony Ibbs <tibs@kynesim.co.uk>
> To: Linux-embedded <linux-embedded@vger.kernel.org>
> Cc: Grant Likely <grant.likely@secretlab.com>, Tibs at home <tibs@tonyibbs.co.uk>, Richard Watts <rrw@kynesim.co.uk>
> Subject: [RFC][PATCH] KBUS messaging subsystem
>
>
[...]
> We've got a working repository with Linux 2.6.37 patched for KBUS,
> available via:
>
> git pull git://github.com/crazyscot/linux-2.6-kbus.git kbus-2.6.37
>
> Our tentative patch is at
> http://kbus.googlecode.com/files/0001-KBUS-messaging-subsystem.patch
>
> The diffstat for the patch is:
>
> Documentation/Kbus.txt | 1189 ++++++++++
> include/linux/kbus_defns.h | 666 ++++++
> init/Kconfig | 3 +
> ipc/Kconfig | 99 +
> ipc/Makefile | 1 +
> ipc/kbus.c | 5120 ++++++++++++++++++++++++++++++++++++++++++++
> ipc/kbus_internal.h | 773 +++++++
> 7 files changed, 7851 insertions(+), 0 deletions(-)
>
> Should I just submit the patch to this list?
Yes. If you want review, then posting a URLs doesn't help. :-) Send
it as an email so that I can just hit 'reply' and start typing.
Post and then I'll comment.
g.
next parent reply other threads:[~2011-02-02 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110128180158.6f670a51@spoon>
2011-02-02 3:40 ` Grant Likely [this message]
2011-02-03 17:04 ` [RFC][PATCH] KBUS messaging subsystem Tony Ibbs
2011-02-03 17:32 ` Grant Likely
2011-02-06 21:07 ` Tony Ibbs
2011-01-28 17:50 Tony Ibbs
2011-01-28 19:20 ` Sam Ravnborg
2011-02-03 16:59 ` 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=20110202034008.GC29148@angua.secretlab.ca \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).