From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Paulo Pavacic <pavacic.p@gmail.com>
Cc: neil.armstrong@linaro.org, sam@ravnborg.org, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: display: panel: add fannal,c3004
Date: Wed, 7 Jun 2023 11:56:15 +0200 [thread overview]
Message-ID: <4b26898c-0751-14c4-1fdf-2c4e59d4f224@linaro.org> (raw)
In-Reply-To: <CAO9szn3+u_yuWb5y_aQGWA8RhW2=qPVcxcZvGWz8MbHH_DamNg@mail.gmail.com>
On 07/06/2023 11:29, Paulo Pavacic wrote:
> Hello Krzysztof,
>
> uto, 6. lip 2023. u 16:43 Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> napisao je:
>>
>> On 06/06/2023 16:07, Paulo Pavacic wrote:
>>> Added fannal to vendor-prefixes and dt bindings for Fannal C3004.
>>> Fannal C3004 is a 480x800 MIPI DSI Panel which requires
>>> DCS initialization sequences with certain delays between certain
>>> commands.
>>>
>>> Signed-off-by: Paulo Pavacic <pavacic.p@gmail.com>
>>> ---
>>> v4 changelog:
>>> - add spaces between properties
>>
>> ???
>
> Added empty lines between properties in yml file
>
>>
>> I pointed out last incorrect versioning. This is v3, not v4. Or is it v4?
>
> It is v4 of the patch but v3 of the patchset. I wasn't sure whether
> somebody would complain if I were to name [patch 2/3] in a patch set
> with different version. I will try to edit changelog to match patchset
> version.
Please maintain consistent versioning. There is only one version -
that's the version you are sending.
>
>>
>> What about my tag?
>>
>
> I have changed in MAINTAINERS file from "+C:
> matrix:r/mipi-dsi-bringup:matrix.org" to " +C:
> matrix:r/linux-drm:matrix.org". So I wasn't sure whether to add it.
> I will add it in future version of the patch.
Keep the tags you received.
>
>> What about my comment?
>>
>
> I thought you wanted me to have more generalized MAINTAINERS community
> URI that's why I have changed it to linux-drm. I will remove community
> URI in future version of the patch.
The chat should be in subsystem entry, not in individual drivers. People
will not hop between 100 IRC rooms to figure out discussion. Just like
we have only one mailing list dedicated to given topic.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-07 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:07 [PATCH v3 0/3] drm/panel: add fannal c3004 panel Paulo Pavacic
2023-06-06 14:07 ` [PATCH v3 1/3] dt-bindings: add fannal vendor prefix Paulo Pavacic
2023-06-06 14:42 ` Krzysztof Kozlowski
2023-06-06 14:07 ` [PATCH v3 2/3] dt-bindings: display: panel: add fannal,c3004 Paulo Pavacic
2023-06-06 14:43 ` Krzysztof Kozlowski
2023-06-07 9:29 ` Paulo Pavacic
2023-06-07 9:56 ` Krzysztof Kozlowski [this message]
2023-06-06 14:07 ` [PATCH v3 3/3] drm/panel-fannal-c3004: Add fannal c3004 DSI panel Paulo Pavacic
2023-06-06 14:45 ` Krzysztof Kozlowski
2023-06-07 13:38 ` Paulo Pavacic
2023-06-07 13:57 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b26898c-0751-14c4-1fdf-2c4e59d4f224@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=pavacic.p@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).