Hi, > Why are you adding this? > > I suspect it's because checkpatch complains that commits with BUG: in > the commit message should be CC'd to stable. (Although, I can't trigger > that warning now. Weird).
> Are you planning to manually backport it? If so, you could CC stable > and then when you get the email that it doesn't apply, then you can do > the manual backport. Or you could ignore it. > > Or if you think it's not worth backporting, you could explain why. > > Cc: <[email protected]> # too risky for low benefit Ah - I added that to try and avoid the failed apply email! It's a bug that only exists in 6.18 and that stable tree will be EOL soon with the 6.19 release, so I figured it's not worth a manual backport. > If a patch doesn't apply, then the stable scripts aren't going to apply > it. It's not necessary to tell the scripts not to try. To me the > "noautosel" basically means that it's important to not backport the > patch. Maybe the API has changed so backporting it will cause a subtle > breakage. Thanks! I wasn't aware of that connotation - I'll resend without it. Shenghao
