From: kernel test robot <yujie.liu@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Raag Jadav <raag.jadav@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 2/2] pinctrl: intel: Add a generic Intel pin control platform driver
Date: Tue, 14 Nov 2023 09:46:07 +0800 [thread overview]
Message-ID: <202311140345.etMnKZeR-lkp@intel.com> (raw)
In-Reply-To: <20231113123147.4075203-3-andriy.shevchenko@linux.intel.com>
Hi Andy,
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 linus/master v6.7-rc1 next-20231113]
[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/Andy-Shevchenko/pinctrl-intel-Revert-Unexport-intel_pinctrl_probe/20231113-204318
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
patch link: https://lore.kernel.org/r/20231113123147.4075203-3-andriy.shevchenko%40linux.intel.com
patch subject: [PATCH v2 2/2] pinctrl: intel: Add a generic Intel pin control platform driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20231114/202311140345.etMnKZeR-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231114/202311140345.etMnKZeR-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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202311140345.etMnKZeR-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/x86/include/asm/percpu.h:27,
from arch/x86/include/asm/nospec-branch.h:14,
from arch/x86/include/asm/paravirt_types.h:27,
from arch/x86/include/asm/ptrace.h:97,
from arch/x86/include/asm/math_emu.h:5,
from arch/x86/include/asm/processor.h:13,
from arch/x86/include/asm/timex.h:5,
from include/linux/timex.h:67,
from include/linux/time32.h:13,
from include/linux/time.h:60,
from include/linux/stat.h:19,
from include/linux/module.h:13,
from drivers/pinctrl/intel/pinctrl-intel-platform.c:10:
>> drivers/pinctrl/intel/pinctrl-intel-platform.c:217:37: error: 'intel_pinctrl_pm_ops' undeclared here (not in a function); did you mean 'intel_pinctrl_probe'?
217 | .pm = pm_sleep_ptr(&intel_pinctrl_pm_ops),
| ^~~~~~~~~~~~~~~~~~~~
include/linux/kernel.h:54:44: note: in definition of macro 'PTR_IF'
54 | #define PTR_IF(cond, ptr) ((cond) ? (ptr) : NULL)
| ^~~
drivers/pinctrl/intel/pinctrl-intel-platform.c:217:23: note: in expansion of macro 'pm_sleep_ptr'
217 | .pm = pm_sleep_ptr(&intel_pinctrl_pm_ops),
| ^~~~~~~~~~~~
vim +217 drivers/pinctrl/intel/pinctrl-intel-platform.c
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 211
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 212 static struct platform_driver intel_platform_pinctrl_driver = {
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 213 .probe = intel_platform_pinctrl_probe,
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 214 .driver = {
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 215 .name = "intel-pinctrl",
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 216 .acpi_match_table = intel_platform_pinctrl_acpi_match,
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 @217 .pm = pm_sleep_ptr(&intel_pinctrl_pm_ops),
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 218 },
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 219 };
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 220 module_platform_driver(intel_platform_pinctrl_driver);
5dacd710dc5f8ca8 Andy Shevchenko 2023-11-13 221
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-14 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 12:28 [PATCH v2 0/2] pinctrl: intel: Add generic platform driver Andy Shevchenko
2023-11-13 12:28 ` [PATCH v2 1/2] pinctrl: intel: Revert "Unexport intel_pinctrl_probe()" Andy Shevchenko
2023-11-13 12:28 ` [PATCH v2 2/2] pinctrl: intel: Add a generic Intel pin control platform driver Andy Shevchenko
2023-11-14 1:46 ` kernel test robot [this message]
2023-11-14 11:41 ` Andy Shevchenko
2023-11-14 11:50 ` Mika Westerberg
2023-11-14 12:11 ` Andy Shevchenko
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=202311140345.etMnKZeR-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raag.jadav@intel.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