mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	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
Subject: Re: [PATCH v2] docs: submitting-patches: Clarify half-baked review tags
Date: Thu, 5 Nov 2026 16:14:27 +0200	[thread overview]
Message-ID: <auyPQ_y10mSfkUNw@ashevche-desk.local> (raw)
In-Reply-To: <a0a17a91-02d1-4c54-8989-ff483a3300ab@oss.qualcomm.com>

On Thu, Nov 05, 2026 at 01:56:10PM +0100, Krzysztof Kozlowski wrote:
> On 05/11/2026 12:53, Andy Shevchenko wrote:
> > On Thu, Nov 05, 2026 at 01:19:14PM +0200, Wolfram Sang wrote:
> >>
> >>>>> "Reviewed-by:, instead, indicates that *the patch* has been reviewed and
> >>>>> found acceptable according to the Reviewer's Statement:"
> >>>>
> >>>> So, for the SPI patch: if someone spent time and reviewed the complex
> >>>> core changes, but only 2 out of dozens of drivers, this would be an Ack
> >>>> according to you. I would, however, understand that this person doesn't
> >>>
> >>> No, and I explained this in this commit msg. That person reviewed the
> >>> MAIN concept of the patch.
> >>
> >> With that MAIN concept emphasized, I am okay with your reasoning and
> >> agree. Before (I cite, upmost paragraph) "*the patch*" could be
> >> interpreted as 100% of the patch (including dumb driver conversions).
> > 
> > ...which may lead to discouragement of reviewing such a patch.
> > At least that's how I read the point.
> 
> Why Ack instead of Review would discourage?

Because Ack doesn't imply *any* review.

> Are you saying people give Reviewed-by tags for incomplete reviews only because they want the credits?

No. We seem to discuss different issues. You are talking about the credits,
and I'm talking about the fact of the review versus acknowledgement.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-11-05 14:14 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 [this message]
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
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=auyPQ_y10mSfkUNw@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --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®