linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: align LED node names with dtschema
Date: Mon, 28 Nov 2022 08:17:41 +0100	[thread overview]
Message-ID: <669d0399-dbc7-965a-9e50-017f017ca823@linaro.org> (raw)
In-Reply-To: <c89f9330-715f-4830-49fb-64c0b533ed39@linaro.org>

Hi Krzysztof,

Le 27/11/2022 à 20:07, Krzysztof Kozlowski a écrit :
> On 27/11/2022 14:33, Neil Armstrong wrote:
>>
>> Le 27/11/2022 à 13:25, Krzysztof Kozlowski a écrit :
>>> On 26/11/2022 17:03, Neil Armstrong wrote:
>>>>>>> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
>>>>>> Aren't you maintainer of the platform? This means I should take care of
>>>>>> this patch?
>>>>> Ah, this will be picked up by Kevin or Jerome? So this tag means only
>>>>> Reviewer's statement of oversight, right?
>>>> Of course I'll pick it.
>>>>
>>> So that's confusing to see Review which does not mean review, but
>>> maintainer pick...
>>
>> Reviewed-by means reviewed, there's no confusion here, the significance
>> is clearly documented on https://docs.kernel.org/process/submitting-patches.html
>>
>>>
>>> Reviewed-by means, I should take your tag and add to v2 or the
>>> maintainer will add it when picking up.
>>
>> Reviewed-by means reviewed, fully reviewed patches are ready to
>> be picked unless a change is asked by a reviewer.
>>
>> Decision to pick or not a patch does not depend on any tags, but
>> is the sole decision of the maintainer adding it's Signed-off-by.
> 
> Then why giving review tag and not notifying about the pick, while the
> pick actually happens? This is confusing. When the maintainer, which is
> supposed to pick patch, gives reviewed it means always the same as
> acked, so the patch is expected to go other way. Not through that
> maintainer's tree.
> 
> If you just apply it, say you apply it.

This last reply goes beyond acceptability on my side, this thread
went too far and I'll stop replying further after this.

If your goal was to kindly ask me to use Acked-by to notify you I'll
pick the patch in the future, while this "rule" is only implicit,
the actual form is far from it.

Concerning this patch, since I already sent the ARM64 DT PR for v6.2,
and I usually don't take new changes except urgent ones after rc6, I'll
pick this patch and "20221125144120.476933-1-krzysztof.kozlowski@linaro.org"
after the next merge window and you'll be notified as I always do.

> 
> Best regards,
> Krzysztof
> 

Neil

  reply	other threads:[~2022-11-28  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 14:41 [PATCH] arm64: dts: amlogic: align LED node names with dtschema Krzysztof Kozlowski
2022-11-25 17:16 ` Neil Armstrong
2022-11-26 14:16   ` Krzysztof Kozlowski
2022-11-26 14:24     ` Krzysztof Kozlowski
2022-11-26 16:03       ` Neil Armstrong
2022-11-27 12:25         ` Krzysztof Kozlowski
2022-11-27 13:33           ` Neil Armstrong
2022-11-27 19:07             ` Krzysztof Kozlowski
2022-11-28  7:17               ` Neil Armstrong [this message]
2022-11-25 22:55 ` Martin Blumenstingl
2023-01-02  9:45 ` Neil Armstrong

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=669d0399-dbc7-965a-9e50-017f017ca823@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=robh+dt@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 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).