Re: linux-next: build failure in final build

Linus Walleij <[email protected]> Sat, 1 Aug 2026 00:03:20 +0200
Newsgroups org.kernel.vger.linux-next,org.kernel.vger.linux-kernel
Message-ID <CAD++jL=DCXDsJJJ6C5WU2FX_YEHnnZrso_jDGiapTTNafa8Uug@mail.gmail.com>
On Thu, Jul 30, 2026 at 5:01=E2=80=AFPM Mark Brown <[email protected]> wro=
te:

> After in the final build, today's linux-next build (arm64 allyesconfig)
> failed like this:
>
> /tmp/next/build/drivers/pinctrl/nxp/pinctrl-s32cc.c: In function 's32_pin=
ctrl_probe':
> /tmp/next/build/drivers/pinctrl/nxp/pinctrl-s32cc.c:1565:33: error: assig=
nment to 'int (*)(struct gpio_regmap *, enum gpio_regmap_operation,  unsign=
ed int,  unsigned int,  unsigned int *, unsigned int *)' from incompatible =
pointer type 'int (*)(struct gpio_regmap *, unsigned int,  unsigned int,  u=
nsigned int *, unsigned int *)' [-Wincompatible-pointer-types]
>  1565 |         gpio_cfg.reg_mask_xlate =3D s32_gpio_reg_mask_xlate;
>       |                                 ^
>
> Caused by commit
>
>     94cb9e8f27079 (pinctrl: s32cc: implement GPIO functionality)
>
> which I have reverted for today.

Nah it's rather caused by
commit 6c53312b7e2d9a972e509f5bac002e169e241eca
from the GPIO tree.

Bartosz do you have an immutable branch for this so I can try to
pull that in and fix up the damager or shall I just revert this commit
and see if it's clean enough to rebase and apply to the GPIO tree instead?

Yours,
Linus Walleij