From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Jason Gunthorpe <jgg@nvidia.com>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The place of AI code review in the Linux Kernel process
Date: Fri, 17 Jul 2026 00:26:47 +0200 [thread overview]
Message-ID: <20260717002647.4830c9fc@foz.lan> (raw)
In-Reply-To: <7ia4pl0oymo0.fsf@castle.c.googlers.com>
On Wed, 15 Jul 2026 21:21:03 +0000
Roman Gushchin <roman.gushchin@linux.dev> wrote:
> >> Many engineers have asked for some sort of interactive mode where they
> >> can ask additional questions or follow up on the initial feedback from
> >> Sashiko. I plan to add this to the local review mode, but for the
> >> central public instance, it is problematic from both security and token
> >> cost perspectives.
> >
> > Could there some way to download the entire context from all the passes
> > to a local environment and have a local llm chew on it to answer
> > questions?
>
> Yeah, it's an option I though about. Like a download button which just
> dumps all relevant context as an .md file, for example.
The better would be to produce, instead, a trained dataset - or - even
better - a patch-review kernel-trained model with a couple of different
sizes (and kv compression), in GGUF format, allowing people to use it
directly, e.g. something that could work like this:
ollama run hf.co/sashiko/sashiko-<some_model>:8b
ollama run hf.co/sashiko/sashiko-<some_model>:36b-a4b
Thanks,
Mauro
next prev parent reply other threads:[~2026-07-16 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 16:55 [MAINTAINERS SUMMIT] The place of AI code review in the Linux Kernel process Roman Gushchin
2026-07-15 17:51 ` Miguel Ojeda
2026-07-15 21:37 ` Roman Gushchin
2026-07-16 15:32 ` Sasha Levin
2026-07-15 17:56 ` Mauro Carvalho Chehab
2026-07-15 18:57 ` Jason Gunthorpe
2026-07-15 21:21 ` Roman Gushchin
2026-07-16 22:26 ` Mauro Carvalho Chehab [this message]
2026-07-15 19:45 ` Dmitry Torokhov
2026-07-16 0:03 ` Steven Rostedt
2026-07-16 0:30 ` SJ Park
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=20260717002647.4830c9fc@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=jgg@nvidia.com \
--cc=ksummit@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
/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.