From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Theodore Tso" <tytso@mit.edu>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Derek Barbosa <debarbos@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
users@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Stephen Finucane <stephenfin@redhat.com>
Subject: Re: Linking Patchwork with Sashiko?
Date: Tue, 21 Jul 2026 17:43:33 +0200 [thread overview]
Message-ID: <20260721174333.67a25aae@localhost> (raw)
In-Reply-To: <20260720211647.3d62f4b9@foz.lan>
On Mon, 20 Jul 2026 21:16:47 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> On Mon, 20 Jul 2026 09:55:37 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Fri, 17 Jul 2026 15:25:59 +0200
> > Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> >
> > > That's one of the reasons why I do think media needs its own custom
> > > prompts.
> >
> > Reading this thread I've come to the conclusion that different systems
> > have different results from Sashiko. Sashko gets confused with some of
> > the tracing logic, but that's because tracing does some hacks to keep
> > the overhead down (it's where live text updates started). It reports
> > issues sometimes that are not a problem due to the way the code was
> > designed.
>
> There is a custom prompt for tracing:
>
> https://github.com/sashiko-dev/sashiko/blob/main/third_party/prompts/kernel/subsystem/tracing.md
>
> Probably, if you run Sashiko without it you would get more false
> positives.
>
> > But I fortunately know of these areas and can easily see when
> > Sashiko falls over it. Hence, these false positives do not waste my
> > time as I'm already aware of them. (I do take a deeper look to make
> > sure it's not reporting something similar that may truly be a bug).
> >
> > But I can see where this could cause a bit more problems with a
> > different sub-system.
> >
> > Hence, I don't believe there should be a one-size-fits-all for the
> > entire kernel,
>
> It is not like that. On static analyzers like Coverity, smatch,
> sparse, coccinelle... there's no space for per-subsystem adjustments.
>
> Now, with LLM, each subsystem may have custom prompts:
>
> https://github.com/sashiko-dev/sashiko/tree/main/third_party/prompts/kernel/subsystem
>
> Also, when LLM parses a C file, it can pick some things from
> the documentation on it.
Btw, Sashiko has gained its first set of adjustments for media today:
https://github.com/sashiko-dev/sashiko/issues/334
https://github.com/sashiko-dev/sashiko/commit/b0aad67f2d5918dd5da768fde15a144f8435d387
https://github.com/sashiko-dev/sashiko/commit/8ac8e51fd79c8560404efe62d0c9ce38defce5af
Hopefully, it will help to prevent some false positives noticed on
past reviews.
--
Thanks,
Mauro
next prev parent reply other threads:[~2026-07-21 15:43 UTC|newest]
Thread overview: 127+ 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-09-20 22:26 ` Peter
2026-09-20 22:31 ` Peter
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-17 9:40 ` Paolo Bonzini
2026-07-17 12:20 ` Theodore Tso
2026-07-17 13:25 ` Mauro Carvalho Chehab
2026-07-20 13:55 ` Steven Rostedt
2026-07-20 14:26 ` Mark Brown
2026-07-20 18:24 ` Steven Rostedt
2026-07-21 16:42 ` Mark Brown
2026-07-21 19:15 ` Steven Rostedt
2026-07-22 14:51 ` Mark Brown
2026-07-22 17:33 ` Theodore Tso
2026-07-23 16:39 ` Mark Brown
2026-07-21 17:12 ` Laurent Pinchart
2026-07-21 19:18 ` Steven Rostedt
2026-07-20 19:16 ` Mauro Carvalho Chehab
2026-07-21 15:43 ` Mauro Carvalho Chehab [this message]
2026-07-17 15:22 ` Nicolas Dufresne
2026-07-21 16:27 ` Laurent Pinchart
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-20 13:36 ` Steven Rostedt
2026-07-21 0:34 ` Masami Hiramatsu
2026-07-17 12:32 ` Laurent Pinchart
2026-07-20 18:08 ` Steven Rostedt
2026-07-22 4:05 ` Roman Gushchin
2026-07-21 18:25 ` Laurent Pinchart
2026-07-21 19:25 ` Steven Rostedt
2026-07-21 22:46 ` Laurent Pinchart
2026-07-21 23:41 ` Steven Rostedt
2026-07-22 5:06 ` Theodore Tso
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-21 16:01 ` Laurent Pinchart
2026-07-16 7:21 ` Mauro Carvalho Chehab
2026-07-16 13:33 ` Jan Kara
2026-07-21 22:43 ` Laurent Pinchart
2026-07-21 23:44 ` Steven Rostedt
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
2026-07-21 16:03 ` 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 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 22:30 ` Dmitry Torokhov
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=20260721174333.67a25aae@localhost \
--to=mchehab+huawei@kernel.org \
--cc=debarbos@redhat.com \
--cc=jacopo.mondi@ideasonboard.com \
--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.