summaryrefslogtreecommitdiffstats
path: root/scripts/gdb/linux/modules.py
diff options
context:
space:
mode:
authorBjorn Andersson <bjorn.andersson@linaro.org>2021-07-24 20:14:14 -0700
committerGeorgi Djakov <djakov@kernel.org>2021-08-09 20:10:19 +0300
commit8bf5d31c4f06d806ae24a3ba998a2f4eaccfa7c1 (patch)
tree4a75eacb1f2d1a7a0cb1456ea1ebfcc4d5fd6583 /scripts/gdb/linux/modules.py
parentffef0b13bf3ededa07570a2926d13a741a1d5272 (diff)
downloadlinux-stable-8bf5d31c4f06d806ae24a3ba998a2f4eaccfa7c1.tar.gz
linux-stable-8bf5d31c4f06d806ae24a3ba998a2f4eaccfa7c1.tar.bz2
linux-stable-8bf5d31c4f06d806ae24a3ba998a2f4eaccfa7c1.zip
interconnect: qcom: osm-l3: Use driver-specific naming
In situations were the developer screws up by e.g. not giving the OSM nodes unique identifiers the interconnect framework might mix up nodes between the OSM L3 provider and e.g. the RPMh provider. The resulting callstack contains "qcom_icc_set", which is not unique to the OSM L3 provider driver. Once the faulting qcom_icc_set() is identified it's further confusing that "qcom_icc_node" is different between the different drivers. To avoid this confusion, rename the node struct and the setter in the OSM L3 driver to include "osm_l3" in their names. Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Tested-by: Steev Klimaszewski <steev@kali.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Link: https://lore.kernel.org/r/20210725031414.3961227-1-bjorn.andersson@linaro.org Signed-off-by: Georgi Djakov <djakov@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions