From: Weijie Yuan <wy@wyuan.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.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
Subject: Re: [PATCH] docs: submitting-patches: Clarify half-baked review tags
Date: Thu, 5 Nov 2026 16:57:33 +0800 [thread overview]
Message-ID: <auxE_RJJKYf0gPlE@wyuan.org> (raw)
In-Reply-To: <70a3eccf-2f4c-4816-a3d7-cd0a6708b5a9@oss.qualcomm.com>
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> writes:
> On 05/11/2026 09:34, Weijie Yuan wrote:
> > Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> writes:
> >
> >> 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 entire rest including the main concept of the
> >> patch, are not really reviewing "the patch".
> >>
> >> As explained in Submitting Patches document, the "Reviewer's statement
> >> of oversight" is for patch:
> >>
> >> (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 complete, meaning it does not allow implicit variations
> >> "this patch or part of this patch".
> >
> > Agreed.
> >
> >> Reviewing pieces of patch while ignoring the main part of it, is
> >> much closer to Acknowledgment, thus Ack, and "Reviewed-by" credit should
> >> not be applicable.
> >
> > But in this case, I suspect that your "Acked-by" trailer will still be
> > interpreted as an ack of the entire patch in future git logs, rather
> > than a partial ack and/or a partial review.
> >
>
> Which would be fine, Acked-by has that meaning and no one really counts
> Acks or tracks Acks for any metrics or patch quality purposes.
;-) Also makes sense.
(I just posted my last one and found that v2 was also posted, what a
coincidence.)
Thanks!
next prev parent reply other threads:[~2026-11-05 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 17:17 Krzysztof Kozlowski
2026-11-05 8:34 ` Weijie Yuan
2026-11-05 8:54 ` Krzysztof Kozlowski
2026-11-05 8:57 ` Weijie Yuan [this message]
2026-11-05 8:50 ` Markus Elfring
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=auxE_RJJKYf0gPlE@wyuan.org \
--to=wy@wyuan.org \
--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 \
/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®