From: kbuild test robot <lkp@intel.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH 2/5] pinctrl: Add API function pinctrl_gpio_get_direction
Date: Wed, 27 Jun 2018 22:07:34 +0800 [thread overview]
Message-ID: <201806272158.Sx2XpWfR%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180627114904.10890-3-paul@crapouillou.net>
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
Hi Paul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc2 next-20180627]
[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/Paul-Cercueil/pinctrl-Add-core-function-pinmux_gpio_get_direction/20180627-201609
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
config: x86_64-randconfig-x002-201825 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers//pinctrl/core.c: In function 'pinctrl_gpio_get_direction':
>> drivers//pinctrl/core.c:873:8: error: implicit declaration of function 'pinmux_gpio_get_direction'; did you mean 'pinmux_gpio_direction'? [-Werror=implicit-function-declaration]
ret = pinmux_gpio_get_direction(pctldev, range, pin);
^~~~~~~~~~~~~~~~~~~~~~~~~
pinmux_gpio_direction
cc1: some warnings being treated as errors
vim +873 drivers//pinctrl/core.c
849
850 /**
851 * pinctrl_gpio_get_direction() - Get the direction (input/output) of a GPIO pin
852 * @gpio: the GPIO pin number from the GPIO subsystem number space
853 *
854 * This function should *ONLY* be used from gpiolib-based GPIO drivers,
855 * as part of their gpio_get_direction() semantics, platforms and individual
856 * drivers shall *NOT* touch pin control GPIO calls.
857 */
858 int pinctrl_gpio_get_direction(unsigned int gpio)
859 {
860 struct pinctrl_dev *pctldev;
861 struct pinctrl_gpio_range *range;
862 int ret;
863 int pin;
864
865 ret = pinctrl_get_device_gpio_range(gpio, &pctldev, &range);
866 if (ret)
867 return ret;
868
869 mutex_lock(&pctldev->mutex);
870
871 /* Convert to the pin controllers number space */
872 pin = gpio_to_pin(range, gpio);
> 873 ret = pinmux_gpio_get_direction(pctldev, range, pin);
874
875 mutex_unlock(&pctldev->mutex);
876
877 return ret;
878 }
879 EXPORT_SYMBOL_GPL(pinctrl_gpio_get_direction);
880
---
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: 33709 bytes --]
next prev parent reply other threads:[~2018-06-27 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 11:48 [PATCH 0/5] pinctrl_gpio_get_direction & ingenic fixes Paul Cercueil
2018-06-27 11:49 ` [PATCH 1/5] pinctrl: Add core function pinmux_gpio_get_direction Paul Cercueil
2018-06-27 11:49 ` [PATCH 2/5] pinctrl: Add API function pinctrl_gpio_get_direction Paul Cercueil
2018-06-27 14:07 ` kbuild test robot [this message]
2018-06-27 15:24 ` kbuild test robot
2018-06-27 11:49 ` [PATCH 3/5] pinctrl: ingenic: Fix inverted direction for < JZ4770 Paul Cercueil
2018-07-09 11:58 ` Linus Walleij
2018-06-27 11:49 ` [PATCH 4/5] pinctrl: ingenic: Implement pinmux callback .gpio_get_direction Paul Cercueil
2018-06-27 11:49 ` [PATCH 5/5] GPIO: ingenic: Implement .get_direction Paul Cercueil
2018-06-27 17:18 ` [PATCH 0/5] pinctrl_gpio_get_direction & ingenic fixes Andy Shevchenko
2018-06-28 19:11 ` Paul Cercueil
2018-06-29 15:29 ` Andy Shevchenko
2018-07-09 12:18 ` Linus Walleij
2018-07-09 12:09 ` Linus Walleij
2018-07-11 23:22 ` Paul Cercueil
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=201806272158.Sx2XpWfR%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=paul@crapouillou.net \
/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®