On Mon, Apr 29, 2024 at 03:28:58PM +0200, Miguel Ojeda wrote: > On Mon, Apr 29, 2024 at 3:27 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > Nope, again, confusion between the Fixes: tag and the # comment. > > Sorry about that (again) -- if you prefer that I avoid Fixes: tag > (when I write # comments), or that I keep the Fixes: tag but that I am > more explicit in these cases (in the # comment), please let me know. Well a Fixes: tag that says "6.1" but yet you only want it applied to 6.6 and newer is quite confusing, don't you think? This implies that 6.1 still has problems and that no one will fix them. That is fine, but just note that it does cause lots of confusion as there are lots of systems out there that trigger lots of things off of those Fixes: tags in order to determine what to do (distro backports, CVE reports, etc.) So when you have a "gap" like this, it usually will mean that well-meaning developers will try to send in backports to that older kernel, despite what your comment said, as that's the "safe" thing to do here. So in the future, try to be consistent one way or the other which mean a fixes tag only with no comment, no fixes tag and just a comment, or a fixes tag that matches the comment. You picked the one other combination that was sure to confuse people, nice work :) thanks, greg k-h
