From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 2/2] gpio: mmio: Parse ngpios property
Date: Thu, 17 Oct 2024 10:05:38 +0800 [thread overview]
Message-ID: <202410170940.KyJaAkpF-lkp@intel.com> (raw)
In-Reply-To: <20241016-gpio-ngpios-v1-2-f16cf154f715@linaro.org>
Hi Linus,
kernel test robot noticed the following build errors:
[auto build test ERROR on 9852d85ec9d492ebef56dc5f229416c925758edc]
url: https://github.com/intel-lab-lkp/linux/commits/Linus-Walleij/dt-bindings-gpio-mmio-Add-ngpios-property/20241016-152354
base: 9852d85ec9d492ebef56dc5f229416c925758edc
patch link: https://lore.kernel.org/r/20241016-gpio-ngpios-v1-2-f16cf154f715%40linaro.org
patch subject: [PATCH 2/2] gpio: mmio: Parse ngpios property
config: i386-buildonly-randconfig-003-20241017 (https://download.01.org/0day-ci/archive/20241017/202410170940.KyJaAkpF-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241017/202410170940.KyJaAkpF-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/202410170940.KyJaAkpF-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpio/gpio-mmio.c:709:10: error: no member named 'ngpios' in 'struct bgpio_pdata'; did you mean 'ngpio'?
709 | pdata->ngpios = ngpios;
| ^~~~~~
| ngpio
include/linux/gpio/driver.h:688:6: note: 'ngpio' declared here
688 | int ngpio;
| ^
1 error generated.
vim +709 drivers/gpio/gpio-mmio.c
693
694 static struct bgpio_pdata *bgpio_parse_fw(struct device *dev, unsigned long *flags)
695 {
696 struct bgpio_pdata *pdata;
697 u32 ngpios;
698
699 if (!dev_fwnode(dev))
700 return NULL;
701
702 pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
703 if (!pdata)
704 return ERR_PTR(-ENOMEM);
705
706 pdata->base = -1;
707
708 if (!device_property_read_u32(dev, "ngpios", &ngpios))
> 709 pdata->ngpios = ngpios;
710
711 if (device_is_big_endian(dev))
712 *flags |= BGPIOF_BIG_ENDIAN_BYTE_ORDER;
713
714 if (device_property_read_bool(dev, "no-output"))
715 *flags |= BGPIOF_NO_OUTPUT;
716
717 return pdata;
718 }
719
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-17 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 7:21 [PATCH 0/2] gpio: mmio: Support ngpios property Linus Walleij
2024-10-16 7:21 ` [PATCH 1/2] dt-bindings: gpio-mmio: Add " Linus Walleij
2024-10-16 15:47 ` Rob Herring
2024-10-16 18:31 ` Linus Walleij
2024-10-16 18:58 ` Rob Herring
2024-10-16 19:12 ` Linus Walleij
2024-10-16 7:21 ` [PATCH 2/2] gpio: mmio: Parse " Linus Walleij
2024-10-17 2:05 ` kernel test robot
2024-10-17 2:05 ` kernel test robot [this message]
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=202410170940.KyJaAkpF-lkp@intel.com \
--to=lkp@intel.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).