From: kernel test robot <lkp@intel.com>
To: "Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Lee Jones <lee@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: [linux-next:master 3007/5901] drivers/video/backlight/ktd2801-backlight.c:16:33: sparse: sparse: symbol 'ktd2801_timing' was not declared. Should it be static?
Date: Sat, 10 Feb 2024 06:43:53 +0800 [thread overview]
Message-ID: <202402100625.M0RkJhMh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 445a555e0623387fa9b94e68e61681717e70200a
commit: 66c76c1cd984c14660453dfa2118014817924375 [3007/5901] backlight: Add Kinetic KTD2801 backlight support
config: arm-randconfig-r111-20240209 (https://download.01.org/0day-ci/archive/20240210/202402100625.M0RkJhMh-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240210/202402100625.M0RkJhMh-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/202402100625.M0RkJhMh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/video/backlight/ktd2801-backlight.c:16:33: sparse: sparse: symbol 'ktd2801_timing' was not declared. Should it be static?
vim +/ktd2801_timing +16 drivers/video/backlight/ktd2801-backlight.c
14
15 /* These values have been extracted from Samsung's driver. */
> 16 const struct expresswire_timing ktd2801_timing = {
17 .poweroff_us = 2600,
18 .detect_delay_us = 150,
19 .detect_us = 270,
20 .data_start_us = 5,
21 .short_bitset_us = 5,
22 .long_bitset_us = 15,
23 .end_of_data_low_us = 10,
24 .end_of_data_high_us = 350
25 };
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-09 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202402100625.M0RkJhMh-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.thompson@linaro.org \
--cc=duje.mihanovic@skole.hr \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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