All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Lee Jones <lee@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: DCO chain of custody revisited (was Re: [PATCH v4 08/11] mfd: qcom-pm8xxx: drop unused PM8018 compatible)
Date: Mon, 31 Oct 2022 13:23:19 -0400	[thread overview]
Message-ID: <20221031172319.znosu3gleyipeje5@meerkat.local> (raw)
In-Reply-To: <7b25ea15b6e508f435ca36967d9f4d4408f9a690.camel@HansenPartnership.com>

On Mon, Oct 31, 2022 at 01:10:58PM -0400, James Bottomley wrote:
> > > Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > Signed-off-by: Lee Jones <lee@kernel.org>
> > 
> > This would indicate that it's *Lee* who is claiming responsibility
> > for collecting the Reviewed-by tag from Krzysztof, because it is in
> > his chain of custody. However, this is not the case -- it was Neil
> > who collected the tag, and therefore the "more correct" order should
> > be:
> > 
> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> > > Signed-off-by: Lee Jones <lee@kernel.org>
> > 
> > If my reasoning is incorrect, then I need to go back to the drawing
> > board.
> 
> You're way over thinking this.

Yes, but it's my job to overthink this, so nobody else has to. :)

> The only tag that matters from the DCO point of view is Signed-off-by.
> That's the ordering we care about for the chain of custody.  All other tags
> are irrelevant.  Of course, it's nice to think that reviews happen *after*
> the code was modified, which is why most of us like to see the Reviewed-by
> after the initial author signoff,

But this is where it becomes complicated. The Reviewed-By trailer was sent to
the v2 of the series, and incorporated into v3(via b4 trailers). If we stick
it below Signed-off-by, then it may suggest that Krzysztof reviewed the v4 of
the patch.

By placing it above the Signed-off-by line, we at least clearly indicate that
it's Neil who put it there.

-K

  reply	other threads:[~2022-10-31 17:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  9:06 [PATCH v4 00/11] arm: qcom: mdm9615: first round of bindings and DT fixes Neil Armstrong
2022-10-21  9:06 ` [PATCH v4 01/11] dt-bindings: arm: qcom: move swir,mangoh-green-wp8548 board documentation to qcom.yaml Neil Armstrong
2022-10-21  9:06 ` [PATCH v4 02/11] arm: dts: qcom: mdm9615*: add SPDX-License-Identifier Neil Armstrong
2022-10-21 13:42   ` Krzysztof Kozlowski
2022-10-21 13:43     ` Krzysztof Kozlowski
2022-10-21  9:06 ` [PATCH v4 03/11] arm: dts: qcom: mdm9615: add missing reg in cpu@0 node Neil Armstrong
2022-10-21  9:14   ` Konrad Dybcio
2022-10-21  9:06 ` [PATCH v4 04/11] arm: dts: qcom: mdm9615: remove invalid spi-max-frequency gsbi3_spi node Neil Armstrong
2022-10-21  9:14   ` Konrad Dybcio
2022-10-21  9:06 ` [PATCH v4 05/11] dt-bindings: mfd: qcom-pm8xxx: document qcom,pm8921 as fallback of qcom,pm8018 Neil Armstrong
2022-10-31 15:31   ` Lee Jones
2022-10-21  9:06 ` [PATCH v4 06/11] dt-bindings: input: qcom,pm8921-pwrkey: convert to dt-schema Neil Armstrong
2022-10-27  7:55   ` Dmitry Torokhov
2022-10-27 12:39     ` Neil Armstrong
2022-10-27 12:43       ` Krzysztof Kozlowski
2022-10-28  0:53         ` Dmitry Torokhov
2022-10-21  9:06 ` [PATCH v4 07/11] dt-bindings: rtc: qcom-pm8xxx: document qcom,pm8921-rtc as fallback of qcom,pm8018-rtc Neil Armstrong
2022-10-21  9:06 ` [PATCH v4 08/11] mfd: qcom-pm8xxx: drop unused PM8018 compatible Neil Armstrong
2022-10-31 15:32   ` Lee Jones
2022-10-31 15:35     ` Neil Armstrong
2022-10-31 16:58       ` DCO chain of custody revisited (was Re: [PATCH v4 08/11] mfd: qcom-pm8xxx: drop unused PM8018 compatible) Konstantin Ryabitsev
2022-10-31 17:10         ` James Bottomley
2022-10-31 17:23           ` Konstantin Ryabitsev [this message]
2022-10-31 17:33             ` James Bottomley
2022-10-31 17:43               ` Konstantin Ryabitsev
2022-10-31 21:29               ` Theodore Ts'o
2022-10-31 17:33             ` Alex Elder
2022-10-31 20:16               ` Willy Tarreau
2022-11-02 19:53             ` Krzysztof Kozlowski
2022-10-31 17:37         ` Michael S. Tsirkin
2022-11-02 14:10     ` [PATCH v4 08/11] mfd: qcom-pm8xxx: drop unused PM8018 compatible Krzysztof Kozlowski
2022-11-02 14:40       ` Lee Jones
2022-10-21  9:06 ` [PATCH v4 09/11] rtc: pm8xxx: drop unused pm8018 compatible Neil Armstrong
2022-10-21  9:16   ` Konrad Dybcio
2022-10-21  9:06 ` [PATCH v4 10/11] arm: dts: qcom: mdm9615: remove invalid interrupt-names from pl18x mmc nodes Neil Armstrong
2022-10-21  9:06 ` [PATCH v4 11/11] arm: dts: qcom: mdm9615: remove useless amba subnode Neil Armstrong
2022-10-21  9:16   ` Konrad Dybcio
2022-11-07  3:12 ` (subset) [PATCH v4 00/11] arm: qcom: mdm9615: first round of bindings and DT fixes Bjorn Andersson

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=20221031172319.znosu3gleyipeje5@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lee@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=tools@linux.kernel.org \
    --cc=users@linux.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.