linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [gpio:devel 53/53] drivers//gpio/gpiolib.c:1402:2: error: 'status' undeclared; did you mean 'kstatfs'?
Date: Thu, 5 Sep 2019 23:22:37 +0200	[thread overview]
Message-ID: <CAMuHMdV75ng-w5KoDAt8=yp0gO=DAU-u9HCy+ydPu+pS9HZhGw@mail.gmail.com> (raw)
In-Reply-To: <201909052108.b1uElYhb%lkp@intel.com>

On Thu, Sep 5, 2019 at 4:04 PM kbuild test robot <lkp@intel.com> 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@intel.com>
>
> 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@linux-m68k.org

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

      reply	other threads:[~2019-09-05 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 13:31 [gpio:devel 53/53] drivers//gpio/gpiolib.c:1402:2: error: 'status' undeclared; did you mean 'kstatfs'? kbuild test robot
2019-09-05 21:22 ` Geert Uytterhoeven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMuHMdV75ng-w5KoDAt8=yp0gO=DAU-u9HCy+ydPu+pS9HZhGw@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=lkp@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).