[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76cab916-782b-45fb-8ef4-52a76bde5530@linaro.org>
Date: Tue, 9 Jan 2024 12:02:10 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Ritesh Kumar <quic_riteshk@...cinc.com>, dri-devel@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: neil.armstrong@...aro.org, quic_jesszhan@...cinc.com, sam@...nborg.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
airlied@...il.com, daniel@...ll.ch, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
quic_abhinavk@...cinc.com, quic_rajeevny@...cinc.com,
quic_vproddut@...cinc.com, sumit.semwal@...aro.org
Subject: Re: [v2 1/2] dt-bindings: display: panel: Add Novatek NT36672E LCD
DSI
On 08/01/2024 11:07, Krzysztof Kozlowski wrote:
> On 08/01/2024 10:59, Ritesh Kumar wrote:
>> Document Novatek NT36672E FHD+ LCD DSI panel.
>>
>> Signed-off-by: Ritesh Kumar <quic_riteshk@...cinc.com>
>>
>> ---
>> v2: Fixed review comments from Krzysztof
>
> Please use standard email subjects, so with the PATCH keyword in the
> title. `git format-patch` helps here to create proper versioned patches.
> Another useful tool is b4. Skipping the PATCH keyword makes filtering of
> emails more difficult thus making the review process less convenient.
That was for the future (I understand making that mistake once with your
v1, but that's v2), no need to resend only for this.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
---
This is an automated instruction, just in case, because many review tags
are being ignored. If you know the process, you can skip it (please do
not feel offended by me posting it here - no bad intentions intended).
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, under or above your Signed-off-by tag. 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.
https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
Best regards,
Krzysztof
Powered by blists - more mailing lists