From: "Theodore Tso" <tytso@mit.edu>
To: August Zeller <augzeller@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
users@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Linking Patchwork with Sashiko?
Date: Thu, 16 Jul 2026 16:54:18 -0400 [thread overview]
Message-ID: <allD8zl_IzTAS7Nl@mit.edu> (raw)
In-Reply-To: <eab30fce0d18137800ce7a77ee1083f11aa1a770.camel@gmail.com>
On Thu, Jul 16, 2026 at 05:10:11PM -0500, August Zeller wrote:
> 2. On the other hand, it is also true that LLMs and derived tools are a
> comprehensive manifestation of the problems of the industry and there
> are valid ethical concerns regarding access discrimination, copyright,
> workload externalization, job loss, etc.
Also, there are multiple ways that LLMs can be used, and questions
about access discrimination, copyright, etc. are *different* if what
we are talking about vibe coding versus code review.
The original question in this thread was *only* about Sashiko, which
is a code review tool. Making general arguments about all LLM use
cases is not helpful, and the policies that we might have for
reviewing or teseting code might be **very** different compared to
vibe coding. For example, copyright concerns simply don't apply.
Can we please avoid conflating all AI use cases? This leads to more
heat rather than light.
- Ted
next prev parent reply other threads:[~2026-07-16 20:54 UTC|newest]
Thread overview: 93+ 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
2026-07-16 13:33 ` Jan Kara
2026-07-16 18:24 ` Willy Tarreau
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-16 20:54 ` Theodore Tso [this message]
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 20:54 ` Nicolas Dufresne
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=allD8zl_IzTAS7Nl@mit.edu \
--to=tytso@mit.edu \
--cc=augzeller@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--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