linux-kernel - Re: [PATCH v2] soc: qcom: qmi: use const for struct qmi_elem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166181675992.322065.17670485769129008263.b4-ty@kernel.org>
Date:   Mon, 29 Aug 2022 18:46:09 -0500
From:   Bjorn Andersson <andersson@...nel.org>
To:     Bjorn Andersson <andersson@...nel.org>,
        konrad.dybcio@...ainline.org, agross@...nel.org,
        quic_jjohnson@...cinc.com
Cc:     linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        lkp@...el.com
Subject: Re: [PATCH v2] soc: qcom: qmi: use const for struct qmi_elem_info

On Mon, 22 Aug 2022 08:34:35 -0700, Jeff Johnson wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/1] soc: qcom: qmi: use const for struct qmi_elem_info
      commit: ff6d365898d4d31bd557954c7fc53f38977b491c

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>