On Mon, Oct 12, 2026 at 08:59:31PM -0700, Kees Cook wrote:
On Mon, Oct 12, 2026 at 05:34:50PM -0400, Sasha Levin wrote:
+A stable tag in the sign-off area asks the stable team to backport a commit to
+the stable and longterm trees once it is merged in mainline. The tag syntax is
+described in Documentation/process/stable-kernel-rules.rst. Deciding on a tag
+requires knowing whether the change is stable material, which released kernels
+contain the bug, and whether the fix applies to them.
And I really don't like this redundancy either. The skill should be
strictly as short as it can possibly be and then aim at the _existing_
documentation. If agents are getting something wrong after reading
Documentation/process/stable-kernel-rules.rst, then we need to add the
changes _there_, not in a parallel agent-only file. I would want to see
all these skills designed to give the framework needed by the agent to
find the _existing_ documentation.
w.r.t to your comments on verbosity/duplication on a few of the patches: I'll
try and reduce it, and will run the local test rig I have for this. I'll see
how we can minimize them.
--
Thanks,
Sasha
