On 02/04/2023 13:32, Krzysztof Kozlowski wrote:
On 02/04/2023 12:25, Dmitry Baryshkov wrote:
On Sun, 2 Apr 2023 at 12:42, Krzysztof Kozlowski
<krzysztof.kozlowski@xxxxxxxxxx> wrote:
On 02/04/2023 00:07, Dmitry Baryshkov wrote:
Following the commit c0ee8e0ba5cc ("arm64: dts: qcom: pmk8350: Use the
correct PON compatible") and commit f46ef374e0dc ("arm64: dts: qcom:
pmk8350: Specify PBS register for PON") use "qcom,pmk8350-pon" compat
string and add RBS region to the PON device.
Fixes: ccd3517faf18 ("arm64: dts: qcom: sc8280xp: Add reference device")
There is no compatible qcom,pmk8350-pon documented at ccd3517faf18, so
backporting it there is incorrect. qcom,pmk8350-pon is neither in v5.19
nor in v6.0.
Well, according to Documentation/process/submitting-patches.rst, Fixes
tag is about noting that there was an issue fixed in the commit. The
mentioned commit has an issue, as the device should have a second
Depends. If device was working in some limited way with old compatible
and one region, there is nothing to fix maybe. It was just incomplete.
If second region is needed for the work, then only that commit should be
marked as fix. Changing compatible is not a fix of that submission
because at the time, the compatible was correct. That time in Git
history, the "qcom,pmk8350-pon" was not correct.
Ack, so we have to backport the schema too.
region. I did not intend to have this patch backported (no Cc stable).
If I were, I could have also added a Cc stable # 5.19.x 03fccdc76dce.
AUTOSEL will backport it anyway, if you do not mention otherwise.
Is there a way to influence AUTOSEL to make it also pick up another commit?
Best regards,
Krzysztof
--
With best wishes
Dmitry
