mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v2] docs: submitting-patches: Clarify half-baked review tags
Date: Thu, 5 Nov 2026 11:55:59 +0100	[thread overview]
Message-ID: <179b3509-7002-4437-965e-e0e47e59a444@oss.qualcomm.com> (raw)
In-Reply-To: <auxQ_ZYMHYJPStox@ashevche-desk.local>

On 05/11/2026 10:48, Andy Shevchenko wrote:
> On Thu, Nov 05, 2026 at 10:27:17AM +0100, Krzysztof Kozlowski wrote:
>> On 05/11/2026 10:19, Andy Shevchenko wrote:
>>> On Thu, Nov 05, 2026 at 09:27:30AM +0100, Krzysztof Kozlowski wrote:
>>>> Refactoring of driver subsystems or some core driver parts often come
>>>> with change of the actual drivers.  If that happens within one patch,
>>>> people giving "Reviewed-by" tag only to piece of the patch, like one
>>>> driver, and ignoring the rest including the main concept of the patch,
>>>> are not really reviewing "the patch".
>>>>
>>>> As explained in the Submitting Patches document, the "Reviewer's
>>>> statement of oversight" is for patch as in "entire patch" meaning:
>>>>
>>>>   (a) I have carried out a technical review of this patch to
>>>>       evaluate its appropriateness and readiness for inclusion into
>>>>       the mainline kernel.
>>>>
>>>> The sentence is explicit and complete, meaning it does not allow
>>>> implicit variations like: "this patch or part of this patch".
>>>>
>>>> Reviewing pieces of the patch while ignoring the main part of it, is
>>>> much closer to Acknowledgment, thus Ack, and "Reviewed-by" credit should
>>>> not be applicable.
>>>
>>> I strongly disagree. It's all explained in the plenty threads you have started
>>> on the Subject.
>>
>> Please provide arguments. You keep responding "No" or "Disagree", yet yo
>> do not give any technical, discussible data.
>>
>> You just wrote:
>> https://lore.kernel.org/all/auxGom0XR-Hax9b3@ashevche-desk.local/
>>
>> "No, (partial) Rb != Ack."
>>
>> to which I provided several quotes backing my point of view:
>> https://lore.kernel.org/all/00390a20-7630-4066-9779-06c8f915a176@kernel.org/
>>
>>> TL;DR: As a reviewer for the piece in question I have done my part fully. It's
>>> not my issue that the piece is bundled into a single patch. We have options:
> 
> ^^^ (1)
> 
>>> 1) ask to split (and review as standalone piece);
>>> 2) add (partial) Rb with the pointers of what exactly has been reviewed;
>>> 3) ignore (silent agreement with the respective subsystem maintainer's opinion);
>>> 4) ...something I forgot?..
>>>
>>> (even partial) Rb != Ack.
>>
>> oh, here you repeat.
>>
>> There is no partial review tag. Please read arguments I already provided
>> to you and either respond with counter arguments or just stop repeating
>> empty statements.
> 
> I already provided you the argument, you seems missed it (see 1 ^^^).

The (1) above does not address that statement of oversight does not
include possibility of partial review.

Best regards,
Krzysztof

  reply	other threads:[~2026-11-05 10:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  8:27 Krzysztof Kozlowski
2026-11-05  8:50 ` Wolfram Sang
2026-11-05  8:57   ` Krzysztof Kozlowski
2026-11-05  9:06     ` Wolfram Sang
2026-11-05  9:12       ` Krzysztof Kozlowski
2026-11-05  9:26         ` Andy Shevchenko
2026-11-05 10:59           ` Krzysztof Kozlowski
2026-11-05  9:28         ` Wolfram Sang
2026-11-05 11:03           ` Krzysztof Kozlowski
2026-11-05 11:19             ` Wolfram Sang
2026-11-05 11:53               ` Andy Shevchenko
2026-11-05 12:56                 ` Krzysztof Kozlowski
2026-11-05 14:14                   ` Andy Shevchenko
2026-11-05  9:29       ` Geert Uytterhoeven
2026-11-05  9:44         ` Wolfram Sang
2026-11-05  9:47           ` Andy Shevchenko
2026-11-05  9:19 ` Andy Shevchenko
2026-11-05  9:27   ` Krzysztof Kozlowski
2026-11-05  9:48     ` Andy Shevchenko
2026-11-05 10:55       ` Krzysztof Kozlowski [this message]
2026-11-05  9:30   ` Jürgen Groß
2026-11-05 15:33     ` Krzysztof Kozlowski
2026-11-05 15:44       ` Juergen Gross
2026-11-05 15:53         ` Krzysztof Kozlowski
2026-11-05 15:59           ` Jürgen Groß
2026-11-05 16:22             ` 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=179b3509-7002-4437-965e-e0e47e59a444@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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®