Thread (17 messages) 17 messages, 4 authors, 2017-03-29

Re: [PATCH 1/3] soc: qcom: smd: Transition client drivers from smd to rpmsg

From: Andy Gross <hidden>
Date: 2017-03-22 21:56:37
Also in: linux-arm-msm, linux-bluetooth, linux-wireless, lkml

On Wed, Mar 22, 2017 at 11:44:39AM -0700, David Miller wrote:
From: Bjorn Andersson <redacted>
Date: Mon, 20 Mar 2017 16:35:42 -0700
quoted
By moving these client drivers to use RPMSG instead of the direct SMD
API we can reuse them ontop of the newly added GLINK wire-protocol
support found in the 820 and 835 Qualcomm platforms.

As the new (RPMSG-based) and old SMD implementations are mutually
exclusive we have to change all client drivers in one commit, to make
sure we have a working system before and after this transition.

Signed-off-by: Bjorn Andersson <redacted>
---

Based on v4.11-rc3 with Arnd's Kconfig dependency fixes for BT_QCOMSMD
(https://lkml.org/lkml/2017/3/20/1038).
Just some questions since I'm supposed to merge this into my net-next
tree.

What is the status of the Kconfig dependency fix and how will I be
getting it?

Second, should I merge all three of these patches to net-next or just
this one?
David,
I ack'd all three.  Please take these through your tree.


Bjorn,
Are we going to need an immutable branch or tag for sychronizing work?

Regards,

Andy Gross
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help