Re: [PATCH v4 0/4] Add Laguna/Tensor G5 SoC and Frankel, Blazer & Mustang boards

[Krzysztof Kozlowski]

On 29/09/2026 12:16, Peter Griffin wrote:
> Hi Krysztof,
> 
> On Tue, 29 Sept 2026 at 11:09, Peter Griffin <peter.griffin@xxxxxxxxxx> wrote:
>>
>> Hi Krysztof,
>>
>> On Tue, 29 Sept 2026 at 10:56, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
>>>
>>> On 29/09/2026 11:41, Krzysztof Kozlowski wrote:
>>>>
>>>> On Fri, 18 Sep 2026 19:05:01 +0000, Peter Griffin wrote:
>>>>> This series adds initial basic support for Laguna (Tensor G5 SoC)
>>>>> found in Frankel (Pixel 10), Blazer (Pixel 10 Pro) and Mustang (Pixel
>>>>> 10 Pro XL) phones.
>>>>>
>>>>> Whilst Tensor G1 to G4 SoCs (found in Pixel 6 to Pixel 9 and Pixel
>>>>> 10a) were offshoots from the Samsung Exynos family. Laguna is an
>>>>> entirely in-house Google designed SoC.
>>>>>
>>>>> [...]
>>>>
>>>> Applied, thanks!
>>>>
>>>> [1/4] dt-bindings: arm: google: Add dt bindings for frankel/blazer/mustang
>>>>       https://git.kernel.org/krzk/linux/c/ecf6405fa6c503c34eb4e7e905957d70d4018e93
>>>> [2/4] arm64: dts: google: Add dts directory for Google-designed silicon
>>>>       https://git.kernel.org/krzk/linux/c/cf3df78629f24b40cd0cb2da74e3ea4a944bed82
>>>> [3/4] arm64: dts: google: Add initial dts for frankel/blazer/mustang
>>>>       https://git.kernel.org/krzk/linux/c/54edd8698bb1fb40c339d0cb2f15baad6993dd48
>>>> [4/4] arm64: defconfig: enable Tensor G5 SoC family
>>>>       https://git.kernel.org/krzk/linux/c/63f674fe8a0a8d6e4bee3e72f7ae658f0e9a0686
>>>>
>>>
>>> This introduces new warnings:
>>>
>>> /home/buildbot/kernel/build/arch/arm64/boot/dts/google/lga.dtsi:368.37-391.5:
>>> Warning (avoid_unnecessary_addr_size):
>>> /soc@0/interrupt-controller@5880000: unnecessary
>>> #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg"
>>> or "ranges" property
>>>
>>> https://krzk.eu/#/builders/28/builds/845
>>>
>>> Probably you wanted address-cells=0?
> 
> Yes, it should be:
> 
> #address-cells = <0>;
> 
> and no size-cells line
> 
> How would you like to handle it? Shall I send a v5, or would you
> prefer to fix it up locally since you already applied it?

Just send a fixup patch.

Best regards,
Krzysztof