From: Lee Jones <lee@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Daniel Golle <daniel@makrotopia.org>, Pavel Machek <pavel@ucw.cz>,
Johannes Berg <johannes.berg@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Richard Purdie <rpurdie@linux.intel.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH] led: trig: timer: stop offloading on deactivation
Date: Thu, 17 Aug 2023 10:16:31 +0100 [thread overview]
Message-ID: <20230817091631.GH648357@google.com> (raw)
In-Reply-To: <202307290641.SUCRTRMI-lkp@intel.com>
On Sat, 29 Jul 2023, kernel test robot wrote:
> Hi Daniel,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on lee-leds/for-leds-next]
> [also build test WARNING on wireless-next/main wireless/main linus/master pavel-leds/for-next v6.5-rc3 next-20230728]
> [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/Daniel-Golle/led-trig-timer-stop-offloading-on-deactivation/20230728-203243
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
> patch link: https://lore.kernel.org/r/728da6e11d34a39f717be07e246dcc4964b0fd51.1690542871.git.daniel%40makrotopia.org
> patch subject: [PATCH] led: trig: timer: stop offloading on deactivation
> config: mips-randconfig-r093-20230728 (https://download.01.org/0day-ci/archive/20230729/202307290641.SUCRTRMI-lkp@intel.com/config)
> compiler: mips-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230729/202307290641.SUCRTRMI-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/202307290641.SUCRTRMI-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> drivers/leds/trigger/ledtrig-timer.c:129:47: sparse: sparse: Using plain integer as NULL pointer
> drivers/leds/trigger/ledtrig-timer.c:129:50: sparse: sparse: Using plain integer as NULL pointer
Are you planning on fixing this?
> vim +129 drivers/leds/trigger/ledtrig-timer.c
>
> 123
> 124 static void timer_trig_deactivate(struct led_classdev *led_cdev)
> 125 {
> 126 /* Stop blinking */
> 127 led_set_brightness(led_cdev, LED_OFF);
> 128 if (led_cdev->blink_set)
> > 129 led_cdev->blink_set(led_cdev, 0, 0);
> 130 }
> 131
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-08-17 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <728da6e11d34a39f717be07e246dcc4964b0fd51.1690542871.git.daniel@makrotopia.org>
2023-07-28 22:55 ` kernel test robot
2023-08-17 9:16 ` Lee Jones [this message]
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=20230817091631.GH648357@google.com \
--to=lee@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=daniel@makrotopia.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=rpurdie@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox