linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-gpio@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [gpio:gpio-variable-naming 19/28] drivers/gpio/gpiolib.c:2748:32: error: 'struct gpio_device' has no member named 'pin_ranges'
Date: Mon, 30 Mar 2020 12:49:51 +0800	[thread overview]
Message-ID: <202003301247.fwDyXOlm%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3376 bytes --]

Hi Thierry,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git gpio-variable-naming
head:   6ce316651a9f236e7204494a4fa080aaf59d5a9d
commit: 2ab73c6d8323fa1eb02c16c07c40ba2ed17da729 [19/28] gpio: Support GPIO controllers without pin-ranges
config: x86_64-randconfig-h002-20200329 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
        git checkout 2ab73c6d8323fa1eb02c16c07c40ba2ed17da729
        # 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 >>):

   In file included from arch/x86/include/asm/bitops.h:16:0,
                    from include/linux/bitops.h:29,
                    from include/linux/bitmap.h:8,
                    from drivers/gpio/gpiolib.c:2:
   drivers/gpio/gpiolib.c: In function 'gpiochip_generic_request':
>> drivers/gpio/gpiolib.c:2748:32: error: 'struct gpio_device' has no member named 'pin_ranges'
     if (!list_empty(&chip->gpiodev->pin_ranges))
                                   ^
   include/linux/compiler.h:58:52: note: in definition of macro '__trace_if_var'
    #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
                                                       ^~~~
   drivers/gpio/gpiolib.c:2748:2: note: in expansion of macro 'if'
     if (!list_empty(&chip->gpiodev->pin_ranges))
     ^~
>> drivers/gpio/gpiolib.c:2748:32: error: 'struct gpio_device' has no member named 'pin_ranges'
     if (!list_empty(&chip->gpiodev->pin_ranges))
                                   ^
   include/linux/compiler.h:58:61: note: in definition of macro '__trace_if_var'
    #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond))
                                                                ^~~~
   drivers/gpio/gpiolib.c:2748:2: note: in expansion of macro 'if'
     if (!list_empty(&chip->gpiodev->pin_ranges))
     ^~
>> drivers/gpio/gpiolib.c:2748:32: error: 'struct gpio_device' has no member named 'pin_ranges'
     if (!list_empty(&chip->gpiodev->pin_ranges))
                                   ^
   include/linux/compiler.h:69:3: note: in definition of macro '__trace_if_value'
     (cond) ?     \
      ^~~~
   include/linux/compiler.h:56:28: note: in expansion of macro '__trace_if_var'
    #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__) ) )
                               ^~~~~~~~~~~~~~
   drivers/gpio/gpiolib.c:2748:2: note: in expansion of macro 'if'
     if (!list_empty(&chip->gpiodev->pin_ranges))
     ^~

vim +2748 drivers/gpio/gpiolib.c

  2740	
  2741	/**
  2742	 * gpiochip_generic_request() - request the gpio function for a pin
  2743	 * @chip: the gpiochip owning the GPIO
  2744	 * @offset: the offset of the GPIO to request for GPIO function
  2745	 */
  2746	int gpiochip_generic_request(struct gpio_chip *chip, unsigned offset)
  2747	{
> 2748		if (!list_empty(&chip->gpiodev->pin_ranges))
  2749			return pinctrl_gpio_request(chip->gpiodev->base + offset);
  2750	
  2751		return 0;
  2752	}
  2753	EXPORT_SYMBOL_GPL(gpiochip_generic_request);
  2754	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35718 bytes --]

                 reply	other threads:[~2020-03-30  4:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202003301247.fwDyXOlm%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=treding@nvidia.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).