public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dan Carpenter <error27@gmail.com>,
	Linus Walleij <linusw@kernel.org>,
	AKASHI Takahiro <akashi.tkhro@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Bartosz Golaszewski <brgl@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	arm-scmi@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Khaled Ali Ahmed <Khaled.AliAhmed@arm.com>,
	Michal Simek <monstr@monstr.eu>
Subject: Re: [PATCH v5 1/7] pinctrl: introduce pinctrl_gpio_get_config()
Date: Sun, 22 Mar 2026 15:07:15 +0800	[thread overview]
Message-ID: <202603221553.6g9sSgFm-lkp@intel.com> (raw)
In-Reply-To: <f7a41ed017fba4a0986ffe72e06933cc1bba2406.1774087290.git.dan.carpenter@linaro.org>

Hi Dan,

kernel test robot noticed the following build errors:

[auto build test ERROR on linusw-pinctrl/devel]
[also build test ERROR on linusw-pinctrl/for-next brgl/gpio/for-next linus/master v7.0-rc4 next-20260320]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Dan-Carpenter/pinctrl-introduce-pinctrl_gpio_get_config/20260321-225727
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
patch link:    https://lore.kernel.org/r/f7a41ed017fba4a0986ffe72e06933cc1bba2406.1774087290.git.dan.carpenter%40linaro.org
patch subject: [PATCH v5 1/7] pinctrl: introduce pinctrl_gpio_get_config()
config: loongarch-loongson32_defconfig (https://download.01.org/0day-ci/archive/20260322/202603221553.6g9sSgFm-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 4abb927bacf37f18f6359a41639a6d1b3bffffb5)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260322/202603221553.6g9sSgFm-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603221553.6g9sSgFm-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/pinctrl/core.c:961:8: error: call to undeclared function 'pin_config_get_for_pin'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     961 |         ret = pin_config_get_for_pin(pctldev, pin, config);
         |               ^
   1 error generated.


vim +/pin_config_get_for_pin +961 drivers/pinctrl/core.c

   941	
   942	/**
   943	 * pinctrl_gpio_get_config() - Get the config for a given GPIO pin
   944	 * @gc: GPIO chip structure from the GPIO subsystem
   945	 * @offset: hardware offset of the GPIO relative to the controller
   946	 * @config: the configuration to query.  On success it holds the result
   947	 * Return: 0 on success, negative errno otherwise
   948	 */
   949	int pinctrl_gpio_get_config(struct gpio_chip *gc, unsigned int offset, unsigned long *config)
   950	{
   951		struct pinctrl_gpio_range *range;
   952		struct pinctrl_dev *pctldev;
   953		int ret, pin;
   954	
   955		ret = pinctrl_get_device_gpio_range(gc, offset, &pctldev, &range);
   956		if (ret)
   957			return ret;
   958	
   959		mutex_lock(&pctldev->mutex);
   960		pin = gpio_to_pin(range, gc, offset);
 > 961		ret = pin_config_get_for_pin(pctldev, pin, config);
   962		mutex_unlock(&pctldev->mutex);
   963	
   964		if (ret)
   965			return ret;
   966	
   967		*config = pinconf_to_config_argument(*config);
   968		return 0;
   969	}
   970	EXPORT_SYMBOL_GPL(pinctrl_gpio_get_config);
   971	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-03-22  7:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 10:13 [PATCH v5 0/7] gpio: introduce a gpio driver for SCMI Dan Carpenter
2026-03-21 10:13 ` [PATCH v5 1/7] pinctrl: introduce pinctrl_gpio_get_config() Dan Carpenter
2026-03-22  7:07   ` kernel test robot [this message]
2026-03-23  9:31   ` Andy Shevchenko
2026-03-21 10:13 ` [PATCH v5 2/7] pinctrl: scmi: Add SCMI_PIN_INPUT_VALUE Dan Carpenter
2026-03-21 10:13 ` [PATCH v5 3/7] pinctrl: scmi: Delete PIN_CONFIG_OUTPUT_IMPEDANCE_OHMS support Dan Carpenter
2026-03-21 10:13 ` [PATCH v5 4/7] pinctrl: scmi: ignore PIN_CONFIG_PERSIST_STATE Dan Carpenter
2026-03-21 10:13 ` [PATCH v5 5/7] firmware: arm_scmi: Allow PINCTRL_REQUEST to return EOPNOTSUPP Dan Carpenter
2026-03-21 10:13 ` [PATCH v5 6/7] gpio: dt-bindings: Add bindings for pinctrl based generic gpio driver Dan Carpenter
2026-03-22  9:49   ` Krzysztof Kozlowski
2026-03-21 10:14 ` [PATCH v5 7/7] gpio: gpio-by-pinctrl: add pinctrl based generic GPIO driver Dan Carpenter
2026-03-23 10:05   ` Andy Shevchenko
2026-03-23  9:58 ` [PATCH v5 0/7] gpio: introduce a gpio driver for SCMI Bartosz Golaszewski
2026-03-23 13:39   ` 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=202603221553.6g9sSgFm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Khaled.AliAhmed@arm.com \
    --cc=akashi.tkhro@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=brgl@kernel.org \
    --cc=error27@gmail.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=monstr@monstr.eu \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox