Re: [PATCH v5 3/6] agents: add a skill to determine stable tags

From: Miguel Ojeda

Date: Thu Nov 12 2026 - 02:14:32 EST


On Thu, Nov 12, 2026 at 12:00 AM Theodore Ts'o <tytso@xxxxxxx> wrote:
>
> +Read Documentation/process/stable-kernel-rules.rst. It says which changes go

If the LLM is going to read the file, then I wonder if we should just
clarify this (i.e. the list given below) in that document directly (as
a guide, i.e. still acknowledging that the stable team decides in the
end).

> +Judge a change by what it does, not by how its description labels it: a
> +"cleanup" that releases a resource on an error path fixes a leak. In practice,
> +the stable trees take:

We are adding Rust soundness issues to `stable-kernel-rules.rst` [1],
so if we are going to have this detailed list here, could we please
add a bullet point somewhere in this list like:

- Fixes for Rust soundness issues.

?

Thanks!

[1] https://lore.kernel.org/all/20261020163358.176088-1-ojeda@xxxxxxxxxx/

> + the code it changes. Otherwise, if the Fixes tags are unresolved, so is the
> + stable decision.

When I was reading this, I wondered if "unresolved" had a particular
meaning here. I assume it is referring to the output of the call to
`find-fixes` and how that affects the output of this one. Perhaps
something like:

Otherwise, if the find-fixes skill cannot determine the Fixes tags,
the stable decision cannot be made either.

is clearer, i.e. being a bit more explicit and using the same words as
the last paragraph?

I hope that helps!

Cheers,
Miguel