Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>,
	Roman Gushchin <roman.gushchin@linux.dev>
Cc: debarbos@redhat.com, Arnaldo Carvalho de Melo <acme@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Konstantin Ryabitsev <mricon@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
	sashiko@lists.linux.dev,
	Linux Kernel Workflows <workflows@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org, kfree@google.com
Subject: Re: Stop false review statements
Date: Mon, 18 May 2026 10:12:16 +0200	[thread overview]
Message-ID: <3267e320-99e9-4858-a292-7271abd5b14c@kernel.org> (raw)
In-Reply-To: <2e20badf27b6910d619329841e37d2961556056f@intel.com>

On 18/05/2026 10:04, Jani Nikula wrote:
> On Sat, 16 May 2026, Roman Gushchin <roman.gushchin@linux.dev> wrote:
>>> On May 16, 2026, at 2:33 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>
>>> I find it opposite: clogging commits with useless information, because
>>> some arbitrary and completely closed-source tool did analysis means
>>> nothing to me one year later when I look at the commit in the Git history.
>>
>> This is simple not true: Sashiko is fully open-source, under Apache 2.0 license
>> and the code belongs to LF. Yes, the instance behind sashiko.dev is using
>> Gemini 3.1 Pro LLM, which is not open-source, but it’s not a fundamental limitation - 
>> Sashiko is supporting various LLMs, including open models - it’s just a practical
>> choice: to my knowledge the quality of open models is not on par with frontier closed
>> models and it would require a non-trivial amount of hardware and infrastructure to run
>> an open model at the required scale.
> 
> In the context of the "Reviewed-by: Sashiko" discussion, this actually
> makes it really hard to assess the quality of those reviews. It is
> *currently* using a boatload of tokens with a specific LLM, and I find
> it's often asking pretty good questions.
> 
> People build their reviewer track record and gain trust over time, but
> the reviews from what is portrayed as "Sashiko" heavily depend on the
> models and resources spent in the background. As a maintainer, it's far
> easier (though still laborous) to deal with the negative feedback from
> LLMs than the positive, because you won't really know how rigorous the
> review was when the response is just "LGTM".

And this already happened with reviewed-by statement given to one-liner
patch which still was not good enough for the maintainer:
https://lore.kernel.org/all/ce11a8ba-8ebc-4c09-b6d0-7e98febeae6b@roeck-us.net/

Obviously same applies to humans - they also give Rb which misses some
aspects - but I hope a person would not review such one-liner. Sashiko
did and as well can provide such "review tags" for every little patch,
which is not helping us really.

Best regards,
Krzysztof

  reply	other threads:[~2026-05-18  8:12 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16  8:05 Stop false review statements Krzysztof Kozlowski
2026-05-16 12:11 ` Guenter Roeck
2026-05-16 12:16   ` Krzysztof Kozlowski
2026-05-16 12:23     ` Guenter Roeck
2026-05-16 12:29       ` Krzysztof Kozlowski
2026-05-16 13:24         ` Laurent Pinchart
2026-05-16 13:45           ` Krzysztof Kozlowski
2026-05-16 21:10           ` Mauro Carvalho Chehab
2026-05-17 15:21       ` Jonathan Corbet
2026-05-18  8:22         ` Jani Nikula
2026-05-16 15:20   ` Konstantin Ryabitsev
2026-05-16 15:36     ` Greg KH
2026-05-16 15:41     ` Roman Gushchin
2026-05-16 15:45       ` Greg KH
2026-05-16 15:49         ` Roman Gushchin
2026-05-16 18:28           ` Arnaldo Carvalho de Melo
2026-05-16 21:29             ` Derek Barbosa
2026-05-16 21:33               ` Krzysztof Kozlowski
2026-05-16 21:59                 ` Roman Gushchin
2026-05-17  8:25                   ` Krzysztof Kozlowski
2026-05-17 10:05                   ` Mauro Carvalho Chehab
2026-05-17 10:10                     ` Willy Tarreau
2026-05-17 10:12                     ` Greg KH
2026-05-17 16:29                       ` Theodore Tso
2026-05-17 22:22                         ` Laurent Pinchart
2026-05-17 16:39                       ` Mauro Carvalho Chehab
2026-05-17 17:03                         ` Guenter Roeck
2026-05-17 18:17                         ` Roman Gushchin
2026-05-17 18:56                           ` Mauro Carvalho Chehab
2026-05-18  5:31                             ` Greg KH
2026-05-17 18:57                           ` Theodore Tso
2026-05-17 19:36                             ` Mauro Carvalho Chehab
2026-05-18  8:04                   ` Jani Nikula
2026-05-18  8:12                     ` Krzysztof Kozlowski [this message]
2026-05-18 12:16                     ` Theodore Tso
2026-05-18 12:54                       ` Geert Uytterhoeven
2026-05-18 19:40                       ` Mauro Carvalho Chehab
2026-05-16 18:28           ` Krzysztof Kozlowski
2026-05-16 18:56             ` Roman Gushchin
2026-05-16 19:00               ` Krzysztof Kozlowski
2026-05-16 19:13                 ` Guenter Roeck
2026-05-16 19:25                   ` Guenter Roeck
2026-05-16 19:31                     ` Roman Gushchin
2026-05-16 19:15                 ` Roman Gushchin
2026-05-16 20:41                   ` Theodore Tso
2026-05-17 15:56                   ` Danilo Krummrich
2026-05-17 21:25                     ` Danilo Krummrich
2026-05-18 17:19                     ` Roman Gushchin
2026-05-19 12:23                       ` Danilo Krummrich
2026-05-18  2:12           ` SeongJae Park
2026-05-16 22:32         ` Mauro Carvalho Chehab
  -- strict thread matches above, loose matches on Subject: below --
2026-05-17 19:42 Roman Gushchin
2026-05-17 22:05 ` Mauro Carvalho Chehab
2026-05-17 19:53 Roman Gushchin

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=3267e320-99e9-4858-a292-7271abd5b14c@kernel.org \
    --to=krzk@kernel.org \
    --cc=acme@kernel.org \
    --cc=debarbos@redhat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@intel.com \
    --cc=kfree@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mricon@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sashiko@lists.linux.dev \
    --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