devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christian Marangi <ansuelsmth@gmail.com>,
	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>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH v5 05/20] leds: leds-lp55xx: generalize load_engine function
Date: Sun, 16 Jun 2024 12:37:38 +0800	[thread overview]
Message-ID: <202406161247.DuuZguPR-lkp@intel.com> (raw)
In-Reply-To: <20240615231152.28201-6-ansuelsmth@gmail.com>

Hi Christian,

kernel test robot noticed the following build errors:

[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v6.10-rc3]
[cannot apply to lee-leds/for-leds-next pavel-leds/for-next next-20240613]
[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/Christian-Marangi/dt-bindings-leds-lp55xx-limit-pwr-sel-property-to-ti-lp8501/20240616-071915
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:    https://lore.kernel.org/r/20240615231152.28201-6-ansuelsmth%40gmail.com
patch subject: [PATCH v5 05/20] leds: leds-lp55xx: generalize load_engine function
config: i386-buildonly-randconfig-001-20240616 (https://download.01.org/0day-ci/archive/20240616/202406161247.DuuZguPR-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240616/202406161247.DuuZguPR-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/202406161247.DuuZguPR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/leds/leds-lp55xx-common.c:103:8: error: call to undeclared function 'FIELD_PREP_CONST'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     103 |         val = LP55xx_MODE_LOAD_ENG << LP55xx_MODE_ENGn_SHIFT(idx, cfg->reg_op_mode.shift);
         |               ^
   drivers/leds/leds-lp55xx-common.c:39:40: note: expanded from macro 'LP55xx_MODE_LOAD_ENG'
      39 | #define   LP55xx_MODE_LOAD_ENG         FIELD_PREP_CONST(LP55xx_MODE_ENG_MASK, 0x1)
         |                                        ^
   1 error generated.


vim +/FIELD_PREP_CONST +103 drivers/leds/leds-lp55xx-common.c

    95	
    96	void lp55xx_load_engine(struct lp55xx_chip *chip)
    97	{
    98		enum lp55xx_engine_index idx = chip->engine_idx;
    99		const struct lp55xx_device_config *cfg = chip->cfg;
   100		u8 mask, val;
   101	
   102		mask = LP55xx_MODE_ENGn_MASK(idx, cfg->reg_op_mode.shift);
 > 103		val = LP55xx_MODE_LOAD_ENG << LP55xx_MODE_ENGn_SHIFT(idx, cfg->reg_op_mode.shift);
   104	
   105		lp55xx_update_bits(chip, cfg->reg_op_mode.addr, mask, val);
   106		lp55xx_wait_opmode_done(chip);
   107	}
   108	EXPORT_SYMBOL_GPL(lp55xx_load_engine);
   109	

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

  reply	other threads:[~2024-06-16  4:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 23:11 [PATCH v5 00/20] leds: leds-lp55xx: overhaul driver Christian Marangi
2024-06-15 23:11 ` [PATCH v5 01/20] dt-bindings: leds-lp55xx: limit pwr-sel property to ti,lp8501 Christian Marangi
2024-06-15 23:11 ` [PATCH v5 02/20] dt-bindings: leds-lp55xx: Add new ti,lp5569 compatible Christian Marangi
2024-06-15 23:11 ` [PATCH v5 03/20] leds: leds-lp55xx: generalize stop_all_engine OP Christian Marangi
2024-06-16  4:50   ` kernel test robot
2024-06-15 23:11 ` [PATCH v5 04/20] leds: leds-lp55xx: generalize probe/remove functions Christian Marangi
2024-06-15 23:11 ` [PATCH v5 05/20] leds: leds-lp55xx: generalize load_engine function Christian Marangi
2024-06-16  4:37   ` kernel test robot [this message]
2024-06-16  5:42   ` kernel test robot
2024-06-15 23:11 ` [PATCH v5 06/20] leds: leds-lp55xx: generalize load_engine_and_select_page function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 07/20] leds: leds-lp55xx: generalize run_engine function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 08/20] leds: leds-lp55xx: generalize update_program_memory function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 09/20] leds: leds-lp55xx: generalize firmware_loaded function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 10/20] leds: leds-lp55xx: generalize led_brightness function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 11/20] leds: leds-lp55xx: generalize multicolor_brightness function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 12/20] leds: leds-lp55xx: generalize set_led_current function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 13/20] leds: leds-lp55xx: generalize turn_off_channels function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 14/20] leds: leds-lp55xx: generalize stop_engine function Christian Marangi
2024-06-15 23:11 ` [PATCH v5 15/20] leds: leds-lp55xx: generalize sysfs engine_load and engine_mode Christian Marangi
2024-06-15 23:11 ` [PATCH v5 16/20] leds: leds-lp55xx: generalize sysfs engine_leds Christian Marangi
2024-06-15 23:11 ` [PATCH v5 17/20] leds: leds-lp55xx: generalize sysfs master_fader Christian Marangi
2024-06-15 23:11 ` [PATCH v5 18/20] leds: leds-lp55xx: support ENGINE program up to 128 bytes Christian Marangi
2024-06-15 23:11 ` [PATCH v5 19/20] leds: leds-lp55xx: drop deprecated defines Christian Marangi
2024-06-15 23:11 ` [PATCH v5 20/20] leds: leds-lp5569: Add support for Texas Instruments LP5569 Christian Marangi

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=202406161247.DuuZguPR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pavel@ucw.cz \
    --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).