Hi Dave, >> 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 <bjorn.andersson@xxxxxxxxxx> >> --- >> >> 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? I acked that one separately and added you: [PATCH v2] Bluetooth: btqcomsmd: fix compile-test dependency > Second, should I merge all three of these patches to net-next or just > this one? I think you have to take all 3 patches. Otherwise it will break. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
