[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <116bd8fb-406b-40ae-97b3-1f25759057ea@kernel.org>
Date: Thu, 8 May 2025 17:46:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Bryan Brattlof <bb@...com>
Cc: Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
Tero Kristo <kristo@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: arm: ti: Add binding for AM62L SoCs
On 08/05/2025 15:14, Bryan Brattlof wrote:
> On May 8, 2025 thus sayeth Krzysztof Kozlowski:
>> On Wed, May 07, 2025 at 10:09:19PM GMT, Bryan Brattlof wrote:
>>> Add the binding for TI's AM62L family of devices.
>>>
>>> Signed-off-by: Bryan Brattlof <bb@...com>
>>> ---
>>> Changes in v1:
>>> - separated out devicetree bindings
>>> ---
>>
>> <form letter>
>> This is a friendly reminder during the review process.
>>
>> It looks like you received a tag and forgot to add it.
>>
>> If you do not know the process, here is a short explanation:
>> Please add Acked-by/Reviewed-by/Tested-by tags when posting new
>> versions of patchset, under or above your Signed-off-by tag, unless
>> patch changed significantly (e.g. new properties added to the DT
>> bindings). Tag is "received", when provided in a message replied to you
>> on the mailing list. Tools like b4 can help here. However, there's no
>> need to repost patches *only* to add the tags. The upstream maintainer
>> will do that for tags received on the version they apply.
>>
>> Please read:
>> https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
>>
>> If a tag was not added on purpose, please state why and what changed.
>> </form letter>
>
> My apologies the last version I assumed the Un-Acked[0] comment was a
> request to remove any trailers I picked up from you. I can add them back
> to this patch if you wish
So I brought this confusion. Binding is fine, the discussion was about
syscons and devices and I unacked that syscon.yaml change. Anyway:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists