Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Bjorn Andersson <andersson@kernel.org>
To:     Bjorn Andersson <andersson@kernel.org>,
        konrad.dybcio@somainline.org, agross@kernel.org,
        quic_jjohnson@quicinc.com
Cc:     linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
        lkp@intel.com
Subject: Re: [PATCH v2] soc: qcom: qmi: use const for struct qmi_elem_info
Date:   Mon, 29 Aug 2022 18:46:09 -0500
Message-Id: <166181675992.322065.17670485769129008263.b4-ty@kernel.org>
In-Reply-To: <20220822153435.7856-1-quic_jjohnson@quicinc.com>
References: <20220822153435.7856-1-quic_jjohnson@quicinc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

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@kernel.org>