diff options
| author | Jeff Johnson <quic_jjohnson@quicinc.com> | 2022-08-22 18:34:35 +0300 |
|---|---|---|
| committer | Bjorn Andersson <andersson@kernel.org> | 2022-08-30 01:33:01 +0300 |
| commit | ff6d365898d4d31bd557954c7fc53f38977b491c (patch) | |
| tree | 2cb37b91cf3f2f6555f32483c209323c7023951f /tools/perf/scripts/python/syscall-counts.py | |
| parent | 7eb89c17abd2574f627c1277a15f6ff64bec33a4 (diff) | |
| download | linux-ff6d365898d4d31bd557954c7fc53f38977b491c.tar.xz | |
soc: qcom: qmi: use const for struct qmi_elem_info
Currently all usage of struct qmi_elem_info, which is used to define
the QMI message encoding/decoding rules, does not use const. This
prevents clients from registering const arrays. Since these arrays are
always pre-defined, they should be const, so add the const qualifier
to all places in the QMI interface where struct qmi_elem_info is used.
Once this patch is in place, clients can independently update their
pre-defined arrays to be const, as demonstrated in the QMI sample
code.
Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Link: https://lore.kernel.org/r/20220822153435.7856-1-quic_jjohnson@quicinc.com
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions