| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <538C329C.8060009@mm-sol.com> Date: Mon, 02 Jun 2014 11:15:24 +0300 From: Stanimir Varbanov <svarbanov@...sol.com> To: Bjorn Andersson <bjorn@...o.se> CC: Kumar Gala <galak@...eaurora.org>, Bjorn Andersson <bjorn.andersson@...ymobile.com>, Samuel Ortiz <sameo@...ux.intel.com>, Lee Jones <lee.jones@...aro.org>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Josh Cartwright <joshc@...eaurora.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-arm-msm <linux-arm-msm@...r.kernel.org> Subject: Re: [PATCH 0/3] Qualcomm Resource Power Manager driver Hi Bjorn, Thanks for the patches. <snip> > Lately I've been working on rpm, rpm-smd, smem, smd, smsm, smp2p > patches for mainline. > It could be argued that smd is a bus and should go in drivers/bus, but > for the rest I fear that we just created drivers/soc/qcom as another > dumping ground for things; a "Qualcomm specific drivers/mfd". Do we have some obstacles to not use a "common mailbox framework" for this IPC (shared memory) communication. It looks that it fits very well with our needs for this rpm-regulator and future submitting of smd driver? -- regards, Stan -- 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