When the memory-dump driver isn't built (CONFIG_QCOM_MEMORY_DUMP_V2=n),
an inline version of msm_dump_data_register() will be used that does
nothing. This means that all memory allocated with the intention of
going to msm_dump_data_register() will be leaked.
Fix this by skipping configure_bark_dump() when
CONFIG_QCOM_MEMORY_DUMP_V2 is disabled.
When the memory-dump driver isn't built (CONFIG_QCOM_MEMORY_DUMP_V2=n), an inline version of msm_dump_data_register() will be used that does nothing. This means that all memory allocated with the intention of going to msm_dump_data_register() will be leaked.
Fix this by skipping configure_bark_dump() when CONFIG_QCOM_MEMORY_DUMP_V2 is disabled.
Signed-off-by: Sultan Alsawaf sultan@kerneltoast.com