From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Roman Gushchin <roman.gushchin@linux.dev>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Derek Barbosa <debarbos@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
users@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stephen Finucane <stephenfin@redhat.com>,
bpf <bpf@vger.kernel.org>, Chris Mason <clm@meta.com>,
Christian Brauner <brauner@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: Linking Patchwork with Sashiko?
Date: Wed, 15 Jul 2026 12:38:11 -0700 [thread overview]
Message-ID: <alfgkG4iSC902tZU@google.com> (raw)
In-Reply-To: <20260715174153.GB3846105@ziepe.ca>
On Wed, Jul 15, 2026 at 02:41:53PM -0300, Jason Gunthorpe wrote:
> On Wed, Jul 15, 2026 at 07:39:21PM +0300, Laurent Pinchart wrote:
> > > Yes, assessing whether AI report is "real" is work, but it's not
> > > reasonable to push this work on already overwhelmed maintainers. And
> > > if AI is wrong, again it's the job of the author to convince the
> > > maintainers it's wrong.
> >
> > We disagree on this as well. This would force contributors to constantly
> > justify their value against a machine that is known to produce a
> > non-negligible quantity of nonsense. Furthermore, if those generative AI
> > tools are as good as their supporters claim, the time they free for
> > maintainers should outweight the need workload to triage the comments.
>
> I feel Sashiko and this whole AI world has created alot more work. It
> is not saving time at all. Now I have to go and read every Sashiko
> report to see if there is something important that normal review
> missed. I have fix all the drive by 'this is already broken' stuff it
> finds. We get way more patches than we did before. Now *everything*
> has to be looked at more skeptically if came from some AI slop. I get
> crazy real security reports that need special hand holding now that we
> never got before.
No, we are just becoming aware how awful our code actually is and how
may issues have been overlooked by experienced developers and
maintainers, not even talking about junior contributors.
So save all these "pre-existing issue" reports in todo/ and go over them
when you have a chance.
>
> Even on the submitting side now I have to run patches through all
> kinds of AI tools to have a solid chance to navigate the new guantlet
> upstream.
Yes, I experience the same. But that just shows that we are not perfect
and prone to making mistakes.
>
> We aren't saving time, or creating less work. My hope is we are
> creating better quality, higher security and less bugs.
I believe we are. Hopefully as we are fixing all these pre-existing
issues we will be seeing less of them...
Thanks.
--
Dmitry
prev parent reply other threads:[~2026-07-15 19:38 UTC|newest]
Thread overview: 66+ 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-15 16:43 ` Laurent Pinchart
2026-07-15 7:59 ` Jacopo Mondi
2026-07-15 8:40 ` Mauro Carvalho Chehab
2026-07-15 17:31 ` Theodore Tso
2026-07-15 12:38 ` Mark Brown
2026-07-15 16:28 ` Laurent Pinchart
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 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-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 19:06 ` Laurent Pinchart
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 [this message]
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=alfgkG4iSC902tZU@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=clm@meta.com \
--cc=debarbos@redhat.com \
--cc=ihor.solodrai@linux.dev \
--cc=jgg@ziepe.ca \
--cc=konstantin@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=stephenfin@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox