Hi, backports are only accepted once the change is merged into main. Once this is the case please use the -x flag while cherry picking.

Isn't there a chicken and egg problem?
This backport is only accepted when the change is merged into main, while the merge into main is only accepted once main switches to using OpenWrt 24.xx. When main uses OpenWrt 24.xx, I can't cherry-pick into the v2023.2.x tree any more because OpenWrt 24.xx already supports the device, so the patch file is missing.

It's accecptable to modify commits / resolve conflicts while cherry picking. Ideally it should probably be noted in the commit message like so (not sure about the most common format to do it, and it's for gluon (and OpenWrt) AFAIK not an enforced policy):

(cherry picked from commit xy)
[added xy/dropped xy/...]

But here's the problem: Gluon is quite restrictive in regards to what downstream patches are accepted (rebasing and managing them is a pain for everyone). I just don't see this happening here.

Therefore i don't think Support for "Sophos AP15C" is going to happen in gluon v2023.2.x. But tbh. i also don't see the necessity in it. If you need it just add the patch as part of your communities build process. And once/if it's available in gluon you can drop it.