Arnd, I noticed that I've had the QCOM_SCM change from Geert in linux-next for a little while now and would prefer not to rebase my tree. I do believe per our other discussion on this subject that QCOM_SCM becomes hidden and therefor shouldn't depend on ARCH_QCOM again. Would you prefer me to respin this with a revert of Geert's patch, or can you effectively revert this as you're applying your patches on top? Regards, Bjorn The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f: Linux 5.15-rc1 (2021-09-12 16:28:37 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-drivers-fixes-for-5.15 for you to fetch changes up to 4382c73a12b4cab537176011a36a3c019cb2a04e: firmware: qcom_scm: QCOM_SCM should depend on ARCH_QCOM (2021-09-19 19:58:19 -0500) ---------------------------------------------------------------- Qualcomm driver fixes for v5.15 This restricts the QCOM_SCM driver to depend on ARCH_QCOM, to reduce it's presence after becoming a loadable module. It then fixes a regression in the mdt_loader, where firmware with the hash segment marked as PT_LOAD would no longer be accepted, preventing several MSM8974 and SDM660 devices from loading remoteproc firmware. Lastly it corrects the drvdata associated with the socinfo device during probe, to match that expected by the remove function. ---------------------------------------------------------------- Antonio Martorana (1): soc: qcom: socinfo: Fixed argument passed to platform_set_data() Geert Uytterhoeven (1): firmware: qcom_scm: QCOM_SCM should depend on ARCH_QCOM Shawn Guo (1): soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment drivers/firmware/Kconfig | 2 +- drivers/soc/qcom/mdt_loader.c | 2 +- drivers/soc/qcom/socinfo.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
