All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yuxi Wang <Yuxi.Wang@monolithicpower.com>,
	pavel@ucw.cz, lee@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	wyx137120466@gmail.com
Subject: Re: [PATCH 2/2] leds: add mp3326 driver
Date: Sun, 26 Nov 2023 05:05:04 +0800	[thread overview]
Message-ID: <202311260403.PyY8h5Dj-lkp@intel.com> (raw)
In-Reply-To: <20231124093034.951-3-Yuxi.Wang@monolithicpower.com>

Hi Yuxi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on lee-leds/for-leds-next]
[also build test WARNING on robh/for-next linus/master v6.7-rc2 next-20231124]
[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/Yuxi-Wang/dt-bindings-leds-add-mps-mp3326-LED/20231124-173610
base:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link:    https://lore.kernel.org/r/20231124093034.951-3-Yuxi.Wang%40monolithicpower.com
patch subject: [PATCH 2/2] leds: add mp3326 driver
config: x86_64-randconfig-123-20231126 (https://download.01.org/0day-ci/archive/20231126/202311260403.PyY8h5Dj-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231126/202311260403.PyY8h5Dj-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/202311260403.PyY8h5Dj-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/leds/leds-mp3326.c: In function 'mp3326_parse_dt':
   drivers/leds/leds-mp3326.c:543:6: warning: unused variable 'val' [-Wunused-variable]
     int val;
         ^~~
   drivers/leds/leds-mp3326.c: At top level:
   drivers/leds/leds-mp3326.c:611:3: error: 'struct i2c_driver' has no member named 'probe_new'; did you mean 'probe'?
     .probe_new = mp3326_leds_probe,
      ^~~~~~~~~
      probe
>> drivers/leds/leds-mp3326.c:611:15: warning: initialization makes integer from pointer without a cast [-Wint-conversion]
     .probe_new = mp3326_leds_probe,
                  ^~~~~~~~~~~~~~~~~
   drivers/leds/leds-mp3326.c:611:15: note: (near initialization for 'mp3326_driver.class')
   drivers/leds/leds-mp3326.c:611:15: error: initializer element is not computable at load time
   drivers/leds/leds-mp3326.c:611:15: note: (near initialization for 'mp3326_driver.class')


vim +611 drivers/leds/leds-mp3326.c

   609	
   610	static struct i2c_driver mp3326_driver = {
 > 611		.probe_new = mp3326_leds_probe,
   612		.driver = {
   613				.name = "mp3326_led",
   614				.of_match_table = mp3326_of_match,
   615			   },
   616		.id_table = mp3326_id,
   617	};
   618	

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

  parent reply	other threads:[~2023-11-25 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  9:30 [PATCH 0/2] leds: Add a driver for MP3326 Yuxi Wang
2023-11-24  9:30 ` [PATCH 1/2] dt-bindings: leds: add mps mp3326 LED Yuxi Wang
2023-11-25 10:44   ` Krzysztof Kozlowski
2023-11-24  9:30 ` [PATCH 2/2] leds: add mp3326 driver Yuxi Wang
2023-11-24 15:42   ` kernel test robot
2023-11-25 20:00   ` kernel test robot
2023-11-25 21:05   ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  3:29 [PATCH 0/2] " Yuxi Wang
2023-11-08  3:29 ` [PATCH 2/2] " Yuxi Wang
2023-11-12 11:21   ` kernel test robot
2023-10-31  7:01 Yuxi (Yuxi) Wang
2023-10-31  8:16 ` Krzysztof Kozlowski

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=202311260403.PyY8h5Dj-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Yuxi.Wang@monolithicpower.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@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+dt@kernel.org \
    --cc=wyx137120466@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.