On Fri, 18 Aug 2023, Michael Schmitz wrote:
Cc: <stable@xxxxxxxxxxxxxxx> # 5.14
5.14+ ? But I do not think you need to specify anything anyway since
you have the Fixes tag.
5.14+ perhaps. I'll check the docs again to see whether Fixes: obsoletes
the stable backport tag. I've so far used both together...
You'd specify a "# x.y+" limit along with a "Fixes" tag if you don't want
to backport as far back as the buggy commit (because some other
pre-requisite isn't present on the older branches). But that does not
apply in this case.
Writing "# 5.14" is surprising because (according to www.kernel.org
landing page) that branch was abandoned, and no live branch was named.
But in "git log" you can see that people write this anyway.
Writing "# 5.14+" or "# 5.15+" is clear enough but is normally omitted
when it can be inferred from the Fixes tag. That's been my experience, at
least.
