Re: [gpio:devel 53/53] drivers//gpio/gpiolib.c:1402:2: error: 'status' undeclared; did you mean 'kstatfs'?

[Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>]

On Thu, Sep 5, 2019 at 4:04 PM kbuild test robot <lkp@xxxxxxxxx> wrote:
> tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
> head:   151a41014bff92f353263cadc051435dc9c3258e
> commit: 151a41014bff92f353263cadc051435dc9c3258e [53/53] Merge tag 'v5.3-rc7' into devel
> config: x86_64-lkp (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
> reproduce:
>         git checkout 151a41014bff92f353263cadc051435dc9c3258e
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@xxxxxxxxx>
>
> All errors (new ones prefixed by >>):
>
>    drivers//gpio/gpiolib.c: In function 'gpiochip_add_data_with_key':
> >> drivers//gpio/gpiolib.c:1402:2: error: 'status' undeclared (first use in this function); did you mean 'kstatfs'?
>      status = gpiochip_irqchip_init_valid_mask(chip);
>      ^~~~~~
>      kstatfs
>    drivers//gpio/gpiolib.c:1402:2: note: each undeclared identifier is reported only once for each function it appears in

Looks like the merge resolution in 151a41014bff92f353263cadc051435dc9c3258e
replaced "status" by "ret", but forgot to update 4 occurrences.

Note that it's still broken in current gpio/for-next.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds