mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@01.org, linux-gpio@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: add COMPILE_TEST to several drivers
Date: Thu, 6 Jul 2017 13:06:58 +0800	[thread overview]
Message-ID: <201707061229.EccZpXTq%fengguang.wu@intel.com> (raw)
In-Reply-To: <1499140313-31592-1-git-send-email-yamada.masahiro@socionext.com>

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

Hi Masahiro,

[auto build test ERROR on gpio/for-next]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Masahiro-Yamada/gpio-add-COMPILE_TEST-to-several-drivers/20170706-070538
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

   drivers//gpio/gpio-vf610.c: In function 'vf610_gpio_direction_input':
>> drivers//gpio/gpio-vf610.c:99:2: error: implicit declaration of function 'pinctrl_gpio_direction_input' [-Werror=implicit-function-declaration]
     return pinctrl_gpio_direction_input(chip->base + gpio);
     ^
   drivers//gpio/gpio-vf610.c: In function 'vf610_gpio_direction_output':
>> drivers//gpio/gpio-vf610.c:107:2: error: implicit declaration of function 'pinctrl_gpio_direction_output' [-Werror=implicit-function-declaration]
     return pinctrl_gpio_direction_output(chip->base + gpio);
     ^
   cc1: some warnings being treated as errors

vim +/pinctrl_gpio_direction_input +99 drivers//gpio/gpio-vf610.c

7f2691a1 Stefan Agner    2014-10-16   93  	else
7f2691a1 Stefan Agner    2014-10-16   94  		vf610_gpio_writel(mask, port->gpio_base + GPIO_PCOR);
7f2691a1 Stefan Agner    2014-10-16   95  }
7f2691a1 Stefan Agner    2014-10-16   96  
7f2691a1 Stefan Agner    2014-10-16   97  static int vf610_gpio_direction_input(struct gpio_chip *chip, unsigned gpio)
7f2691a1 Stefan Agner    2014-10-16   98  {
7f2691a1 Stefan Agner    2014-10-16  @99  	return pinctrl_gpio_direction_input(chip->base + gpio);
7f2691a1 Stefan Agner    2014-10-16  100  }
7f2691a1 Stefan Agner    2014-10-16  101  
7f2691a1 Stefan Agner    2014-10-16  102  static int vf610_gpio_direction_output(struct gpio_chip *chip, unsigned gpio,
7f2691a1 Stefan Agner    2014-10-16  103  				       int value)
7f2691a1 Stefan Agner    2014-10-16  104  {
7f2691a1 Stefan Agner    2014-10-16  105  	vf610_gpio_set(chip, gpio, value);
7f2691a1 Stefan Agner    2014-10-16  106  
7f2691a1 Stefan Agner    2014-10-16 @107  	return pinctrl_gpio_direction_output(chip->base + gpio);
7f2691a1 Stefan Agner    2014-10-16  108  }
7f2691a1 Stefan Agner    2014-10-16  109  
bd0b9ac4 Thomas Gleixner 2015-09-14  110  static void vf610_gpio_irq_handler(struct irq_desc *desc)

:::::: The code at line 99 was first introduced by commit
:::::: 7f2691a19627a8d7723909b6e82468fd4437e445 gpio: vf610: add gpiolib/IRQ chip driver for Vybrid

:::::: TO: Stefan Agner <stefan@agner.ch>
:::::: CC: Linus Walleij <linus.walleij@linaro.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

  reply	other threads:[~2017-07-06  5:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  3:51 Masahiro Yamada
2017-07-06  5:06 ` kbuild test robot [this message]
2017-07-06 21:52 ` Linus Walleij

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=201707061229.EccZpXTq%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®