From: kernel test robot <lkp@intel.com>
To: Kyle Swenson <kyle.swenson@est.tech>,
pavel@ucw.cz, robh+dt@kernel.org, krzk+dt@kernel.org
Cc: kbuild-all@lists.01.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, Kyle Swenson <kyle.swenson@est.tech>
Subject: Re: [PATCH 1/2] leds: aw21024: Add support for Awinic's AW21024
Date: Mon, 16 May 2022 18:42:28 +0800 [thread overview]
Message-ID: <202205161859.bDAFU09i-lkp@intel.com> (raw)
In-Reply-To: <20220513190409.3682501-1-kyle.swenson@est.tech>
Hi Kyle,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on pavel-leds/for-next]
[also build test WARNING on robh/for-next v5.18-rc7 next-20220513]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Kyle-Swenson/leds-aw21024-Add-support-for-Awinic-s-AW21024/20220514-030705
base: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
config: x86_64-randconfig-r011-20220516 (https://download.01.org/0day-ci/archive/20220516/202205161859.bDAFU09i-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/38eeda60299918b5599f4a58714dc91f9741677c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Kyle-Swenson/leds-aw21024-Add-support-for-Awinic-s-AW21024/20220514-030705
git checkout 38eeda60299918b5599f4a58714dc91f9741677c
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/leds/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/leds/leds-aw21024.c:295:34: warning: 'of_aw21024_leds_match' defined but not used [-Wunused-const-variable=]
295 | static const struct of_device_id of_aw21024_leds_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~
vim +/of_aw21024_leds_match +295 drivers/leds/leds-aw21024.c
294
> 295 static const struct of_device_id of_aw21024_leds_match[] = {
296 { .compatible = "awinic,aw21024", },
297 {},
298 };
299 MODULE_DEVICE_TABLE(of, of_aw21024_leds_match);
300
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-05-16 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 19:04 [PATCH 1/2] leds: aw21024: Add support for Awinic's AW21024 Kyle Swenson
2022-05-13 19:04 ` [PATCH 2/2] dt-bindings: leds: Add aw21024 binding Kyle Swenson
2022-05-13 20:48 ` Rob Herring
2022-05-17 9:08 ` Krzysztof Kozlowski
2022-05-17 18:31 ` Kyle Swenson
2022-05-18 8:17 ` Krzysztof Kozlowski
2022-05-18 21:18 ` Kyle Swenson
2022-05-19 8:04 ` Krzysztof Kozlowski
2022-05-16 10:21 ` [PATCH 1/2] leds: aw21024: Add support for Awinic's AW21024 kernel test robot
2022-05-16 10:42 ` kernel test robot [this message]
2022-05-16 12:34 ` kernel test robot
2022-05-17 9:11 ` Krzysztof Kozlowski
2022-05-17 18:36 ` Kyle Swenson
2022-05-18 8:30 ` 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=202205161859.bDAFU09i-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=krzk+dt@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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).