From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 4/6] leds: pca955x: Use pinctrl to map GPIOs to pins
Date: Fri, 23 Jul 2021 23:24:00 +0800 [thread overview]
Message-ID: <202107232303.QU1hB1Nh-lkp@intel.com> (raw)
In-Reply-To: <20210723075858.376378-5-andrew@aj.id.au>
[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]
Hi Andrew,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on pavel-linux-leds/for-next v5.14-rc2 next-20210723]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Andrew-Jeffery/leds-Fix-pca955x-GPIO-pin-mappings/20210723-160236
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
config: x86_64-randconfig-m001-20210723 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/b0a72adc5668fe81b75d7b10f310d05aea0f3b82
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Andrew-Jeffery/leds-Fix-pca955x-GPIO-pin-mappings/20210723-160236
git checkout b0a72adc5668fe81b75d7b10f310d05aea0f3b82
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/leds/leds-pca955x.o: in function `pca955x_pinmux_get_function_name':
>> drivers/leds/leds-pca955x.c:468: undefined reference to `pinctrl_dev_get_drvdata'
ld: drivers/leds/leds-pca955x.o: in function `pca955x_pinctrl_get_groups_count':
drivers/leds/leds-pca955x.c:406: undefined reference to `pinctrl_dev_get_drvdata'
ld: drivers/leds/leds-pca955x.o: in function `pca955x_pinctrl_get_group_pins':
drivers/leds/leds-pca955x.c:438: undefined reference to `pinctrl_dev_get_drvdata'
ld: drivers/leds/leds-pca955x.o: in function `pca955x_pinctrl_get_group_name':
drivers/leds/leds-pca955x.c:415: undefined reference to `pinctrl_dev_get_drvdata'
ld: drivers/leds/leds-pca955x.o: in function `pca955x_pinmux_get_function_groups':
drivers/leds/leds-pca955x.c:481: undefined reference to `pinctrl_dev_get_drvdata'
ld: drivers/leds/leds-pca955x.o:drivers/leds/leds-pca955x.c:598: more undefined references to `pinctrl_dev_get_drvdata' follow
ld: drivers/leds/leds-pca955x.o: in function `pca955x_probe':
>> drivers/leds/leds-pca955x.c:804: undefined reference to `devm_pinctrl_register_and_init'
>> ld: drivers/leds/leds-pca955x.c:856: undefined reference to `pinctrl_enable'
vim +468 drivers/leds/leds-pca955x.c
464
465 static const char *
466 pca955x_pinmux_get_function_name(struct pinctrl_dev *pctldev, unsigned int selector)
467 {
> 468 struct pca955x *pca955x = pinctrl_dev_get_drvdata(pctldev);
469
470 if (selector != 0)
471 dev_err(&pca955x->client->dev, "Only the 'LED' function is supported");
472
473 return "LED";
474 }
475
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 40978 bytes --]
next prev parent reply other threads:[~2021-07-23 15:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:58 [RFC PATCH 0/6] leds: Fix pca955x GPIO pin mappings Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 1/6] pinctrl: Add pinctrl_gpio_as_pin() Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 16:15 ` kernel test robot
2021-08-10 13:34 ` Linus Walleij
2021-08-10 13:34 ` Linus Walleij
2021-08-11 0:24 ` Andrew Jeffery
2021-08-11 0:24 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 2/6] pinctrl: Add hook for device-specific map parsing Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 3/6] leds: pca955x: Relocate chipdef-related descriptors Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 4/6] leds: pca955x: Use pinctrl to map GPIOs to pins Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 12:40 ` kernel test robot
2021-07-23 15:24 ` kernel test robot [this message]
2021-08-10 13:54 ` Linus Walleij
2021-08-10 13:54 ` Linus Walleij
2021-08-11 0:19 ` Andrew Jeffery
2021-08-11 0:19 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 5/6] ARM: dts: rainier: Add presence-detect and fault indictor GPIO expander Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
2021-07-23 7:58 ` [RFC PATCH 6/6] pinctrl: Check get_group_pins callback on init Andrew Jeffery
2021-07-23 7:58 ` Andrew Jeffery
[not found] ` <CAHp75VeQML7njMZ6x8kC-ZJVexC1xJ6n1cB3JneVMAVfuOJgWw@mail.gmail.com>
2021-07-28 5:43 ` [RFC PATCH 0/6] leds: Fix pca955x GPIO pin mappings Andrew Jeffery
2021-07-28 5:43 ` Andrew Jeffery
2021-07-28 9:13 ` Andy Shevchenko
2021-07-28 9:13 ` Andy Shevchenko
2021-07-29 0:38 ` Andrew Jeffery
2021-07-29 0:38 ` Andrew Jeffery
2021-07-29 7:40 ` Andy Shevchenko
2021-07-29 7:40 ` Andy Shevchenko
2021-08-03 4:07 ` Andrew Jeffery
2021-08-03 4:07 ` Andrew Jeffery
2021-08-03 10:33 ` Andy Shevchenko
2021-08-03 10:33 ` Andy Shevchenko
2021-08-04 4:55 ` Andrew Jeffery
2021-08-04 4:55 ` Andrew Jeffery
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=202107232303.QU1hB1Nh-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.