From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jan Kara <jack@suse.cz>, Theodore Tso <tytso@mit.edu>,
Roman Gushchin <roman.gushchin@linux.dev>,
Derek Barbosa <debarbos@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Steven Rostedt <rostedt@goodmis.org>,
users@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stephen Finucane <stephenfin@redhat.com>
Subject: Re: Linking Patchwork with Sashiko?
Date: Thu, 16 Jul 2026 09:21:20 +0200 [thread overview]
Message-ID: <20260716092120.75c7fca7@foz.lan> (raw)
In-Reply-To: <20260715202808.GN1778116@killaraus.ideasonboard.com>
On Wed, 15 Jul 2026 23:28:08 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> > > Flipping the argument, should contributors be obliged to do extra work
> > > that make them feel diminished as a human ? I'm talking here about
> > > justifying themselves against LLM arguments that have not been analyzed
> > > by a maintainer first.
> >
> > You write here about "feeling diminished" or "justifying themselves" and
> > I'm not sure I get it. If you get a complaint from some CI running
> > checkpatch or say coverity which is bogus (or perhaps correct?), do you
> > also feel diminished or needing to justify? I just don't see how LLMs are
> > different here...
>
> No, I don't get the same feeling. This is due to multiple factors. One
> of them is due to the more deterministic nature of those tools. I know a
> build failure from the 0day bot is a build failure. I know what warnings
> from checkpatch can be ignored in a given subsystem.
Not quite true: smatch is not deterministic: it depends on a database
it builds from previous runs.
https://github.com/error27/smatch/blob/master/Documentation/smatch.rst#using-smatch
> I know that I can
> reply to some reported issues saying they're false positives and won't
> be asked for a full justification.
Just like any bot review, there's no need to justify obvious things,
but the way to make reviewers/maintainers aware of false positives is
to reply. That's how our process have been working all those years.
Thanks,
Mauro
next prev parent reply other threads:[~2026-07-16 7:21 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260528144627.1ae09ff2@foz.lan>
[not found] ` <1372F826-5513-4EB2-AE27-1DC0D2DE0AEB@linux.dev>
[not found] ` <20260529083100.6710b6cd@foz.lan>
[not found] ` <20260529083801.2c7e8990@foz.lan>
[not found] ` <ahmwUk0uXTkdwohf@debarbos-thinkpadt14gen5.rmtusma.csb>
2026-05-30 8:30 ` Linking Patchwork with Sashiko? Mauro Carvalho Chehab
2026-05-30 15:57 ` Roman Gushchin
2026-05-30 18:00 ` Mauro Carvalho Chehab
2026-05-30 18:49 ` Mauro Carvalho Chehab
2026-05-30 18:53 ` Mauro Carvalho Chehab
2026-06-02 15:51 ` Derek Barbosa
2026-06-02 16:51 ` Mauro Carvalho Chehab
2026-06-02 18:39 ` Jason Gunthorpe
2026-06-02 20:29 ` Mauro Carvalho Chehab
2026-06-02 20:13 ` Roman Gushchin
2026-06-02 20:39 ` Mauro Carvalho Chehab
2026-06-02 20:44 ` Roman Gushchin
2026-06-02 23:50 ` Matthieu Baerts
2026-06-03 3:35 ` Mauro Carvalho Chehab
2026-06-03 3:49 ` Roman Gushchin
2026-06-04 6:52 ` Mauro Carvalho Chehab
2026-06-07 17:56 ` Mauro Carvalho Chehab
2026-06-30 20:32 ` Derek Barbosa
2026-07-10 5:45 ` Mauro Carvalho Chehab
2026-07-10 6:39 ` Mauro Carvalho Chehab
2026-07-11 1:01 ` Roman Gushchin
2026-07-13 7:55 ` Mauro Carvalho Chehab
2026-07-13 9:41 ` Laurent Pinchart
2026-07-13 20:04 ` Mauro Carvalho Chehab
2026-07-14 22:55 ` Roman Gushchin
2026-07-15 0:59 ` Laurent Pinchart
2026-07-15 2:00 ` Roman Gushchin
2026-07-15 3:06 ` Linus Torvalds
2026-07-15 12:21 ` Jori Koolstra
2026-07-15 16:50 ` Steven Rostedt
2026-07-15 18:13 ` Nicolas Dufresne
2026-07-15 19:12 ` Laurent Pinchart
2026-07-15 19:27 ` Nicolas Dufresne
2026-07-15 20:03 ` Laurent Pinchart
2026-07-16 15:04 ` August Zeller
2026-07-15 16:43 ` Laurent Pinchart
2026-07-15 23:28 ` lyude
2026-07-15 7:59 ` Jacopo Mondi
2026-07-15 8:40 ` Mauro Carvalho Chehab
2026-07-15 17:31 ` Theodore Tso
2026-07-16 8:07 ` Jacopo Mondi
2026-07-15 12:38 ` Mark Brown
2026-07-15 16:28 ` Laurent Pinchart
2026-07-15 21:08 ` Roman Gushchin
2026-07-15 23:20 ` Steven Rostedt
2026-07-16 0:09 ` Roman Gushchin
2026-07-15 3:54 ` Theodore Tso
2026-07-15 7:13 ` Mauro Carvalho Chehab
2026-07-15 12:42 ` James Bottomley
2026-07-15 16:18 ` Laurent Pinchart
2026-07-15 16:53 ` James Bottomley
2026-07-15 17:09 ` Laurent Pinchart
2026-07-15 16:11 ` Laurent Pinchart
2026-07-15 17:00 ` Jan Kara
2026-07-15 20:28 ` Laurent Pinchart
2026-07-15 20:36 ` James Bottomley
2026-07-15 20:42 ` Laurent Pinchart
2026-07-16 0:14 ` Roman Gushchin
2026-07-16 7:04 ` Mauro Carvalho Chehab
2026-07-15 23:32 ` Steven Rostedt
2026-07-16 0:03 ` Roman Gushchin
2026-07-16 7:21 ` Mauro Carvalho Chehab [this message]
2026-07-16 13:33 ` Jan Kara
2026-07-15 17:14 ` Theodore Tso
2026-07-15 17:35 ` Miguel Ojeda
2026-07-15 17:41 ` Laurent Pinchart
2026-07-15 18:18 ` Linus Torvalds
2026-07-15 18:51 ` Laurent Pinchart
2026-07-15 19:14 ` Linus Torvalds
2026-07-15 20:13 ` Laurent Pinchart
2026-07-16 9:20 ` Giacomo Tesio
2026-07-16 15:10 ` August Zeller
2026-07-15 16:28 ` Ihor Solodrai
2026-07-15 16:39 ` Laurent Pinchart
2026-07-15 17:12 ` Ihor Solodrai
2026-07-15 17:35 ` Mark Brown
2026-07-15 18:39 ` Ihor Solodrai
2026-07-15 20:32 ` Mark Brown
2026-07-15 19:06 ` Laurent Pinchart
2026-07-15 21:13 ` Theodore Tso
2026-07-16 3:00 ` Nicolas Dufresne
2026-07-16 3:53 ` Theodore Tso
2026-07-16 7:55 ` Mauro Carvalho Chehab
2026-07-16 6:23 ` Jai Luthra
2026-07-16 12:32 ` Theodore Tso
2026-07-15 17:41 ` Jason Gunthorpe
2026-07-15 19:10 ` Laurent Pinchart
2026-07-15 19:55 ` Mark Brown
2026-07-15 19:38 ` Dmitry Torokhov
2026-07-15 21:27 voste62ocr
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=20260716092120.75c7fca7@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=debarbos@redhat.com \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=konstantin@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=stephenfin@redhat.com \
--cc=tytso@mit.edu \
--cc=users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.