From: "David Lanzendörfer" <david.lanzendoerfer@o2s.ch>
To: linux-arm-msm@vger.kernel.org
Subject: "Kernel side RPC server bundle"
Date: Sat, 17 Jul 2010 17:23:13 +0200 [thread overview]
Message-ID: <201007171723.16822.david.lanzendoerfer@o2s.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
hi all
I wanted to ask, how your position is to this rpc stuff, we have in androids
kernel branch.
There they have intoduced some layer system to communicate between smartphone
and "real" phone parts.
Would it be allowed into official kernel?
Or are we obligated to use already existent proc_comm?
/me is asking, because I'm not sure, if its worth the work to port it to the
recent branch and create a patch.
best regards
leviathan
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-07-17 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 15:23 David Lanzendörfer [this message]
2010-07-28 0:50 ` "Kernel side RPC server bundle" David Brown
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=201007171723.16822.david.lanzendoerfer@o2s.ch \
--to=david.lanzendoerfer@o2s.ch \
--cc=linux-arm-msm@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).