From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: richard.leitner@linux.dev,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [PATCH RESEND v2 1/2] dt-bindings: display: simple: add support for InnoLux G070ACE-L01
Date: Fri, 21 Apr 2023 19:01:27 +0200 [thread overview]
Message-ID: <2d7d8462-4e75-bbd2-4ae5-6403eda43020@linaro.org> (raw)
In-Reply-To: <CAD=FV=WLHpddAMo7GQwj98TtDn0xw6UzgYUKyVhSDZw1acKpCg@mail.gmail.com>
On 21/04/2023 18:51, Doug Anderson wrote:
>>> ...and, again, it matches the order that I thought was right. In other
>>> words, the patch file generated says:
>>>
>>>> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
>>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> We talk about `b4 trailers`, because the tag is applied by the
>> submitter, not by the maintainer.
>>
>>>
>>> Did I get something wrong in the above?
>>
>> Your `b4 am` will of course put the tag later, because it is you who
>> applies the tag.
>
> Ah, got it. So I guess from the perspective of "b4" every time the
> author modifies a patch (like adding new tags to it) then it's a new
> application of Signed-off-by and thus the old Signed-off-by is removed
> from the top and a new one is added below all the tags that have been
> received. Thus if b4 grabs all the tags off the mailing list for
> applying it ends up in a different order than if it grabs all the tags
> off the mailing list for sending a new version.
>
> OK, I can understand that perspective. I'll keep it in mind.
Yeah. I actually agree with your point that submitter's SoB should
always be the last one, but I agree more with using process via
standardized tools. IOW, since I cannot change in this matter b4, I need
to agree with it. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-21 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 7:50 [PATCH RESEND v2 0/2] panel-simple: Add InnoLux G070ACE-L01 support richard.leitner
2023-03-13 7:50 ` [PATCH RESEND v2 1/2] dt-bindings: display: simple: add support for InnoLux G070ACE-L01 richard.leitner
2023-04-21 16:15 ` Doug Anderson
2023-04-21 16:26 ` Krzysztof Kozlowski
2023-04-21 16:37 ` Doug Anderson
2023-04-21 16:45 ` Krzysztof Kozlowski
2023-04-21 16:51 ` Doug Anderson
2023-04-21 17:01 ` Krzysztof Kozlowski [this message]
2023-04-21 18:32 ` Konstantin Ryabitsev
2023-03-13 7:50 ` [PATCH RESEND v2 2/2] drm/panel: simple: Add " richard.leitner
2023-04-21 16:15 ` Doug Anderson
2023-04-11 9:28 ` [PATCH RESEND v2 0/2] panel-simple: Add InnoLux G070ACE-L01 support Richard Leitner
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=2d7d8462-4e75-bbd2-4ae5-6403eda43020@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.leitner@linux.dev \
--cc=richard.leitner@skidata.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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
all inboxes | Powered by JetHome®