All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Matheus Castello <matheus@castello.eng.br>
Cc: kbuild-all@01.org, linus.walleij@linaro.org,
	linux-kernel@vger.kernel.org,
	Matheus Castello <matheus@castello.eng.br>
Subject: Re: [PATCH v1 2/2] pinctrl: generic: improve apply_setting error verbosity
Date: Tue, 1 May 2018 18:05:47 +0800	[thread overview]
Message-ID: <201805011855.LvT1SKBS%fengguang.wu@intel.com> (raw)
In-Reply-To: <1525160437-5222-3-git-send-email-matheus@castello.eng.br>

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

Hi Matheus,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.17-rc3 next-20180501]
[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/Matheus-Castello/pinctrl-generic-improve-apply_setting-error-verbosity/20180501-160704
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
config: x86_64-randconfig-s2-05011559 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers//pinctrl/pinconf.c: In function 'pinconf_apply_setting':
>> drivers//pinctrl/pinconf.c:177:5: error: implicit declaration of function 'pinconf_generic_get_param_property_name' [-Werror=implicit-function-declaration]
        pinconf_generic_get_param_property_name(
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers//pinctrl/pinconf.c:175:26: warning: format '%s' expects argument of type 'char *', but argument 5 has type 'int' [-Wformat=]
        "%s error %d seting %s for pin %d\n",
                             ^
   cc1: some warnings being treated as errors

vim +/pinconf_generic_get_param_property_name +177 drivers//pinctrl/pinconf.c

   150	
   151	int pinconf_apply_setting(const struct pinctrl_setting *setting)
   152	{
   153		struct pinctrl_dev *pctldev = setting->pctldev;
   154		const struct pinconf_ops *ops = pctldev->desc->confops;
   155		int ret;
   156	
   157		if (!ops) {
   158			dev_err(pctldev->dev, "missing confops\n");
   159			return -EINVAL;
   160		}
   161	
   162		switch (setting->type) {
   163		case PIN_MAP_TYPE_CONFIGS_PIN:
   164			if (!ops->pin_config_set) {
   165				dev_err(pctldev->dev, "missing pin_config_set op\n");
   166				return -EINVAL;
   167			}
   168			ret = ops->pin_config_set(pctldev,
   169					setting->data.configs.group_or_pin,
   170					setting->data.configs.configs,
   171					setting->data.configs.num_configs);
   172			if (ret < 0) {
   173	#ifdef CONFIG_GENERIC_PINCONF
   174				dev_err(pctldev->dev,
   175					"%s error %d seting %s for pin %d\n",
   176					pctldev->desc->name, ret,
 > 177					pinconf_generic_get_param_property_name(
   178						pctldev, setting->data.configs.num_configs,
   179						setting->data.configs.configs),
   180					setting->data.configs.group_or_pin);
   181	#endif
   182	
   183				dev_err(pctldev->dev,
   184					"pin_config_set op failed for %s pin %d\n",
   185					pctldev->desc->name,
   186					setting->data.configs.group_or_pin);
   187	
   188				return ret;
   189			}
   190			break;
   191		case PIN_MAP_TYPE_CONFIGS_GROUP:
   192			if (!ops->pin_config_group_set) {
   193				dev_err(pctldev->dev,
   194					"missing pin_config_group_set op\n");
   195				return -EINVAL;
   196			}
   197			ret = ops->pin_config_group_set(pctldev,
   198					setting->data.configs.group_or_pin,
   199					setting->data.configs.configs,
   200					setting->data.configs.num_configs);
   201			if (ret < 0) {
   202				dev_err(pctldev->dev,
   203					"pin_config_group_set op failed for group %d\n",
   204					setting->data.configs.group_or_pin);
   205				return ret;
   206			}
   207			break;
   208		default:
   209			return -EINVAL;
   210		}
   211	
   212		return 0;
   213	}
   214	

---
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: 32961 bytes --]

  parent reply	other threads:[~2018-05-01 10:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  7:40 [PATCH v1 0/2] pinctrl: generic: improve apply_setting error verbosity Matheus Castello
2018-05-01  7:40 ` [PATCH v1 1/2] pinctrl: generic: add API to solve generic sub-node property name Matheus Castello
2018-05-01  7:40 ` [PATCH v1 2/2] pinctrl: generic: improve apply_setting error verbosity Matheus Castello
2018-05-01  8:34   ` kbuild test robot
2018-05-01 10:05   ` kbuild test robot [this message]
2018-05-01 19:09     ` [PATCH v2 0/2] " Matheus Castello
2018-05-01 19:10       ` [PATCH v2 1/2] pinctrl: generic: add API to solve generic sub-node property name Matheus Castello
2018-05-02 12:56         ` Linus Walleij
2018-05-01 19:10       ` [PATCH v2 2/2] pinctrl: generic: improve apply_setting error verbosity Matheus Castello
2018-05-02 12:51         ` Linus Walleij
2018-05-08  5:27           ` Matheus Castello

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=201805011855.LvT1SKBS%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matheus@castello.eng.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.