Re: [PATCH 1/2] Documentation: dt-bindings: arm: qcom: Add Pixel 3 and 3 XL

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 10/6/25 12:09 PM, David Heidelberg wrote:
> On 06/10/2025 10:09, Konrad Dybcio wrote:
>> On 10/6/25 12:21 AM, Dmitry Baryshkov wrote:
>>> On Sun, Oct 05, 2025 at 03:16:28PM +0200, David Heidelberg via B4 Relay wrote:
>>>> From: David Heidelberg <david@ixit.cz>
>>>>
>>>> Document the bindings for the Pixel 3 and 3 XL.
>>>>
>>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>>> ---
>>>>   Documentation/devicetree/bindings/arm/qcom.yaml | 5 ++---
>>>>   1 file changed, 2 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> index ae43b35565808..2190c5b409748 100644
>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> @@ -976,9 +976,8 @@ properties:
>>>>           - items:
>>>>             - enum:
>>>> -              - google,cheza
>>>> -              - google,cheza-rev1
>>>> -              - google,cheza-rev2
>>>
>>> Why are you removing those?
>>
>> I removed these a long time ago, the base for this series is 6.17-release
>> instead of -next :/
> 
> I did purposefully base on 6.17 (and sadly the downgrade from next brought this mess), because the support for Pixel 3 is a bit fragile and as I have only Pixel 3 XL at home (not the Pixel 3, which I always asking someone else to borrow or test for me), I decided to kept 6.17 base so I know it's the state where blueline boots (in case sdm845 or blueline gets broken in the -next).
> 
> If you want me to, I can base the next version on -next.

-next currently contains changes from the past ~3 months, which
you're missing out on

You unfortunately have to rebase, or your patches will simply
generate merge conflicts

Konrad