From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ch-zrh-72-201.trenka.ch ([93.188.72.201]:57487 "EHLO mail.o2s.ch" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1760021Ab0GQPW0 (ORCPT ); Sat, 17 Jul 2010 11:22:26 -0400 From: David =?iso-8859-1?q?Lanzend=F6rfer?= Subject: "Kernel side RPC server bundle" Date: Sat, 17 Jul 2010 17:23:13 +0200 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart24162375.zLCijnVlTM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201007171723.16822.david.lanzendoerfer@o2s.ch> Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: linux-arm-msm@vger.kernel.org --nextPart24162375.zLCijnVlTM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 --nextPart24162375.zLCijnVlTM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkxByuQACgkQAeZw77btGjpYUQCfZufrqlZmMcz9DgPdTDCjL5i4 m1wAoJoxwMYS1ovHkbZ4r2rHpdoAaHcR =4sGT -----END PGP SIGNATURE----- --nextPart24162375.zLCijnVlTM--