From: kernel test robot <lkp@intel.com>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
rogerq@kernel.org, tony@atomide.com, linus.walleij@linaro.org,
brgl@bgdev.pl, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
m-leonard@ti.com, praneeth@ti.com, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v3 3/3] gpio tps65215: Add support for varying gpio/offset values
Date: Sat, 18 Jan 2025 03:34:04 +0800 [thread overview]
Message-ID: <202501180331.d5V1SdDH-lkp@intel.com> (raw)
In-Reply-To: <20250113225530.124213-4-s-ramamoorthy@ti.com>
Hi Shree,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250113]
[cannot apply to tmlind-omap/for-next v6.13-rc7 v6.13-rc6 v6.13-rc5 linus/master v6.13-rc7]
[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/Shree-Ramamoorthy/gpio-tps65215-Add-TPS65215-to-platform_device_id-table/20250114-065813
base: next-20250113
patch link: https://lore.kernel.org/r/20250113225530.124213-4-s-ramamoorthy%40ti.com
patch subject: [PATCH v3 3/3] gpio tps65215: Add support for varying gpio/offset values
config: i386-randconfig-004-20250117 (https://download.01.org/0day-ci/archive/20250118/202501180331.d5V1SdDH-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250118/202501180331.d5V1SdDH-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/202501180331.d5V1SdDH-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpio/gpio-tps65219.c:159:3: error: use of undeclared identifier 'TPS65215'
159 | [TPS65215] = {
| ^
>> drivers/gpio/gpio-tps65219.c:175:15: error: variable has incomplete type 'enum pmic_id'
175 | enum pmic_id chip = platform_get_device_id(pdev)->driver_data;
| ^
drivers/gpio/gpio-tps65219.c:175:7: note: forward declaration of 'enum pmic_id'
175 | enum pmic_id chip = platform_get_device_id(pdev)->driver_data;
| ^
drivers/gpio/gpio-tps65219.c:193:21: error: use of undeclared identifier 'TPS65215'
193 | { "tps65215-gpio", TPS65215 },
| ^
drivers/gpio/gpio-tps65219.c:197:1: error: definition of variable with array type needs an explicit size or an initializer
197 | MODULE_DEVICE_TABLE(platform, tps6521x_gpio_id_table);
| ^
include/linux/module.h:250:21: note: expanded from macro 'MODULE_DEVICE_TABLE'
250 | extern typeof(name) __mod_device_table__##type##__##name \
| ^
<scratch space>:249:1: note: expanded from here
249 | __mod_device_table__platform__tps6521x_gpio_id_table
| ^
4 errors generated.
vim +175 drivers/gpio/gpio-tps65219.c
168
169 static int tps65219_gpio_probe(struct platform_device *pdev)
170 {
171 struct tps65219_gpio *gpio;
172 const struct tps65219_chip_data *pmic;
173
174 struct tps65219 *tps = dev_get_drvdata(pdev->dev.parent);
> 175 enum pmic_id chip = platform_get_device_id(pdev)->driver_data;
176 pmic = &chip_info_table[chip];
177
178 gpio = devm_kzalloc(&pdev->dev, sizeof(*gpio), GFP_KERNEL);
179 if (!gpio)
180 return -ENOMEM;
181
182 gpio->tps = tps;
183 gpio->gpio_chip = tps65219_template_chip;
184 gpio->gpio_chip.label = dev_name(&pdev->dev);
185 gpio->gpio_chip.ngpio = pmic->ngpio;
186 gpio->gpio_chip.offset = pmic->offset;
187 gpio->gpio_chip.parent = tps->dev;
188
189 return devm_gpiochip_add_data(&pdev->dev, &gpio->gpio_chip, gpio);
190 }
191
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-17 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 22:55 [PATCH v3 0/3] Add TI TPS65215 PMIC GPIO Support Shree Ramamoorthy
2025-01-13 22:55 ` [PATCH v3 1/3] gpio: tps65215: Add TPS65215 to platform_device_id table Shree Ramamoorthy
2025-01-17 17:46 ` kernel test robot
2025-01-17 19:33 ` kernel test robot
2025-01-13 22:55 ` [PATCH v3 2/3] gpio: tps65215: Update GPIO0_IDX macro prefix Shree Ramamoorthy
2025-01-13 22:55 ` [PATCH v3 3/3] gpio tps65215: Add support for varying gpio/offset values Shree Ramamoorthy
2025-01-17 19:34 ` kernel test robot [this message]
2025-02-07 8:53 ` [PATCH v3 0/3] Add TI TPS65215 PMIC GPIO Support Bartosz Golaszewski
2025-02-07 17:02 ` Shree Ramamoorthy
2025-02-12 21:12 ` Shree Ramamoorthy
2025-02-13 8:11 ` Bartosz Golaszewski
2025-02-18 17:33 ` Shree Ramamoorthy
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=202501180331.d5V1SdDH-lkp@intel.com \
--to=lkp@intel.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=brgl@bgdev.pl \
--cc=christophe.jaillet@wanadoo.fr \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=m-leonard@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.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