From: kernel test robot <lkp@intel.com>
To: Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/3] [PATCH v5] leds: Add LED1202 I2C driver
Date: Wed, 6 Nov 2024 08:38:35 +0800 [thread overview]
Message-ID: <202411060859.fqkOY75Z-lkp@intel.com> (raw)
In-Reply-To: <20241105161041.4813-3-vicentiu.galanopulo@remote-tech.co.uk>
Hi Vicentiu,
kernel test robot noticed the following build errors:
[auto build test ERROR on lee-leds/for-leds-next]
[also build test ERROR on robh/for-next linus/master v6.12-rc6 next-20241105]
[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/Vicentiu-Galanopulo/dt-bindings-leds-Add-LED1202-LED-Controller/20241106-001305
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link: https://lore.kernel.org/r/20241105161041.4813-3-vicentiu.galanopulo%40remote-tech.co.uk
patch subject: [PATCH 3/3] [PATCH v5] leds: Add LED1202 I2C driver
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20241106/202411060859.fqkOY75Z-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411060859.fqkOY75Z-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/202411060859.fqkOY75Z-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/leds/leds-st1202.c: In function 'st1202_dt_init':
>> drivers/leds/leds-st1202.c:350:49: warning: missing terminating " character
350 | dev_err_probe(dev, err, "Failed to register LED class dev,
| ^
>> drivers/leds/leds-st1202.c:350:49: error: missing terminating " character
350 | dev_err_probe(dev, err, "Failed to register LED class dev,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/leds/leds-st1202.c:351:41: error: 'error' undeclared (first use in this function); did you mean 'err'?
351 | error: %d\n", err);
| ^~~~~
| err
drivers/leds/leds-st1202.c:351:41: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/leds/leds-st1202.c:351:46: error: expected ')' before ':' token
351 | error: %d\n", err);
| ^
| )
drivers/leds/leds-st1202.c:350:38: note: to match this '('
350 | dev_err_probe(dev, err, "Failed to register LED class dev,
| ^
>> drivers/leds/leds-st1202.c:351:50: error: stray '\' in program
351 | error: %d\n", err);
| ^
drivers/leds/leds-st1202.c:351:52: warning: missing terminating " character
351 | error: %d\n", err);
| ^
drivers/leds/leds-st1202.c:351:52: error: missing terminating " character
351 | error: %d\n", err);
| ^~~~~~~~
>> drivers/leds/leds-st1202.c:352:36: error: expected ';' before '}' token
352 | return err;
| ^
| ;
353 | }
| ~
vim +350 drivers/leds/leds-st1202.c
318
319 static int st1202_dt_init(struct st1202_chip *chip)
320 {
321 struct device *dev = &chip->client->dev;
322 struct st1202_led *led;
323 int err, reg;
324
325 for_each_available_child_of_node_scoped(dev_of_node(dev), child) {
326 struct led_init_data init_data = {};
327
328 err = of_property_read_u32(child, "reg", ®);
329 if (err) {
330 of_node_put(child);
331 return dev_err_probe(dev, err, "Invalid register, error: %d\n", err);
332 }
333
334 led = &chip->leds[reg];
335 led->is_active = true;
336 led->fwnode = of_fwnode_handle(child);
337
338 led->led_cdev.max_brightness = U8_MAX;
339 led->led_cdev.brightness_set_blocking = st1202_led_set;
340 led->led_cdev.pattern_set = st1202_led_pattern_set;
341 led->led_cdev.pattern_clear = st1202_led_pattern_clear;
342 led->led_cdev.default_trigger = "pattern";
343
344 init_data.fwnode = led->fwnode;
345 init_data.devicename = "st1202";
346 init_data.default_label = ":";
347 err = devm_led_classdev_register_ext(dev,
348 &led->led_cdev, &init_data);
349 if (err < 0) {
> 350 dev_err_probe(dev, err, "Failed to register LED class dev,
> 351 error: %d\n", err);
> 352 return err;
353 }
354 led->led_cdev.brightness_set = st1202_brightness_set;
355 led->led_cdev.brightness_get = st1202_brightness_get;
356 }
357
358 return 0;
359 }
360
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-06 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 16:10 [PATCH 1/3] [PATCH v3] Documentation:leds: Add leds-st1202.rst Vicentiu Galanopulo
2024-11-05 16:10 ` [PATCH 2/3] [PATCH v4] dt-bindings: leds: Add LED1202 LED Controller Vicentiu Galanopulo
2024-11-05 16:10 ` [PATCH 3/3] [PATCH v5] leds: Add LED1202 I2C driver Vicentiu Galanopulo
2024-11-06 0:38 ` kernel test robot [this message]
2024-11-06 2:03 ` kernel test robot
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=202411060859.fqkOY75Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=vicentiu.galanopulo@remote-tech.co.uk \
/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