If that's the case, this patch has no business bothering upstream maintainers (Guenter, Jean, Jonathan) or the upstream mailing lists (linux-hwmon@, linux-kernel@, linux-doc@). The only people this should be sent to are myself and Joel, and the only list it should be sent to is openbmc@. If you send a backport patch for openbmc/linux and are using `git send- email` to do so, then in nearly all cases you should use the `-- suppress-cc=all` option to make sure upstream maintainers and lists are _not_ automatically copied on the mail. However, if you wish this change to be back-ported to an _upstream_ stable tree (e.g. the v6.6 series), please _first_ familiarise yourself with the stable tree rules, satisfy yourself that the change meets all the requirements and constraints, and only then follow one of the documented processes: https://docs.kernel.org/process/stable-kernel-rules.html#stable-kernel-rules If you have any questions do follow up with myself, Joel and the OpenBMC mailing list, but make sure to exclude the upstream maintainers and lists for now. Thanks, Andrew
