Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
From:   Bjorn Andersson <andersson@kernel.org>
To:     Andy Gross <agross@kernel.org>,
        Konrad Dybcio <konrad.dybcio@linaro.org>,
        Elliot Berman <quic_eberman@quicinc.com>,
        Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>
Cc:     linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org
Subject: Re: [PATCH v3] firmware: qcom_scm: use 64-bit calling convention only when client is 64-bit
Date:   Wed, 27 Sep 2023 17:34:10 -0700
Message-ID: <169586125040.1226038.6973458146206642205.b4-ty@kernel.org>
In-Reply-To: <20230925-scm-v3-1-8790dff6a749@quicinc.com>
References: <20230925-scm-v3-1-8790dff6a749@quicinc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Mon, 25 Sep 2023 13:59:22 +0530, Kathiravan Thirumoorthy wrote:
> Per the "SMC calling convention specification", the 64-bit calling
> convention can only be used when the client is 64-bit. Whereas the
> 32-bit calling convention can be used by either a 32-bit or a 64-bit
> client.
> 
> Currently during SCM probe, irrespective of the client, 64-bit calling
> convention is made, which is incorrect and may lead to the undefined
> behaviour when the client is 32-bit. Let's fix it.
> 
> [...]

Applied, thanks!

[1/1] firmware: qcom_scm: use 64-bit calling convention only when client is 64-bit
      commit: 3337a6fea25370d3d244ec6bb38c71ee86fcf837

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