[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <baf62dd9-2dca-4757-b95d-7842d83c3007@linaro.org>
Date: Thu, 18 Jul 2024 10:21:02 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bjorn Andersson <andersson@...nel.org>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Konrad Dybcio
<konrad.dybcio@...aro.org>, Jagadeesh Kona <quic_jkona@...cinc.com>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Taniya Das <quic_tdas@...cinc.com>,
Satya Priya Kakitapalli <quic_skakitap@...cinc.com>,
Ajit Pandey <quic_ajipan@...cinc.com>,
Imran Shaik <quic_imrashai@...cinc.com>
Subject: Re: (subset) [PATCH V4 0/8] Add support for videocc and camcc on
SM8650
On 26/06/2024 06:30, Bjorn Andersson wrote:
>
> On Sun, 02 Jun 2024 17:14:31 +0530, Jagadeesh Kona wrote:
>> Add support for video and camera clock controllers on Qualcomm SM8650
>> platform.
>>
>> Changes in V4:
>> [PATCH 1/8]: Updated commit text. Replaced :: with : in SM8450 videocc
>> YAML file as Krzysztof's comment in V3
>> [PATCH 5/8]: Replaced :: with : in SM8450 camcc YAML file. Updated commit
>> text and dropped Fixes tag as per Johan's comments in V3
>> Added R-By tags received till V3
>>
>> [...]
>
> Applied, thanks!
>
> [8/8] arm64: dts: qcom: sm8650: Add video and camera clock controllers
> commit: 0bdb730e63f6628b0f8deb3f11991b1d10f9bca5
That's the only message I have that something here was applied, but it
seems entire patchset was applied.
Patchset ended on your branch on 25th of June with HEAD 09ea421652a8
("clk: qcom: camcc-sm8650: Add SM8650 camera clock controller driver")
and it does not compile.
Really, this HEAD does not compile.
This means:
1. This branch has code which was never built by you,
2. This branch has code which was never built by robots,
3. Or none above - so it was built - but reports were ignored.
In case of 1 and 2, can we please check if your tree receives proper LKP
emails about build failures and successes? Or do you build (or anyone
else) your branches?
Later this branch (or head) was sent to arm-soc, so basically for 2-3
weeks this had build failure, which went to upstream maintainer.
Best regards,
Krzysztof
Powered by blists - more mailing lists