9 Oct
2025
9 Oct
'25
4:03 p.m.
On Thu, Oct 9, 2025, at 17:56, Sasha Levin wrote:
- Why it’s needed in stable
- The GPIO subsystem recently made legacy interfaces optional/fenced off, which exposed drivers still using global GPIO numbers. This patch is part of that follow-up hardening: it gates the si476x core on `GPIOLIB_LEGACY`, avoiding invalid build combinations. It is a pure Kconfig fix with no runtime behavior change, directly addressing a regression introduced by the gpiolib changes and thus a textbook stable backport candidate for trees that have those gpiolib changes.
This is incorrect, the patch does not need to be backported because at the moment CONFIG_GPIOLIB_LEGACY is enabled unconditionally, and the coming patch to make it optional will not get backported.
Arnd