From: kernel test robot <lkp@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
lee@kernel.org, pavel@ucw.cz, danielt@kernel.org,
jingoohan1@gmail.com, deller@gmx.de, simona@ffwll.ch
Cc: oe-kbuild-all@lists.linux.dev, linux-leds@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2 08/11] backlight: lcd: Replace fb events with a dedicated function call
Date: Thu, 27 Feb 2025 23:07:50 +0800 [thread overview]
Message-ID: <202502272207.A1uo13Zf-lkp@intel.com> (raw)
In-Reply-To: <20250226093456.147402-9-tzimmermann@suse.de>
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on lee-backlight/for-backlight-next]
[also build test ERROR on lee-leds/for-leds-next linus/master v6.14-rc4 next-20250227]
[cannot apply to lee-backlight/for-backlight-fixes]
[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/Thomas-Zimmermann/fbdev-Rework-fb_blank/20250226-174013
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git for-backlight-next
patch link: https://lore.kernel.org/r/20250226093456.147402-9-tzimmermann%40suse.de
patch subject: [PATCH v2 08/11] backlight: lcd: Replace fb events with a dedicated function call
config: i386-buildonly-randconfig-002-20250227 (https://download.01.org/0day-ci/archive/20250227/202502272207.A1uo13Zf-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502272207.A1uo13Zf-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/202502272207.A1uo13Zf-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
WARNING: modpost: missing MODULE_DESCRIPTION() in fs/exportfs/exportfs.o
>> ERROR: modpost: "lcd_notify_mode_change_all" [drivers/video/fbdev/core/fb.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-27 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:31 [PATCH v2 00/11] backlight, lcd, led: Remove fbdev dependencies Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 01/11] fbdev: Rework fb_blank() Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 02/11] fbdev: Track display blanking state Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 03/11] fbdev: Send old blank state in FB_EVENT_BLANK Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 04/11] backlight: Implement fbdev tracking with blank state from event Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 05/11] backlight: Move blank-state handling into helper Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 06/11] backlight: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-27 11:42 ` kernel test robot
2025-02-27 12:46 ` kernel test robot
2025-02-26 9:31 ` [PATCH v2 07/11] backlight: lcd: Move event handling into helpers Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 08/11] backlight: lcd: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-27 15:07 ` kernel test robot [this message]
2025-02-26 9:31 ` [PATCH v2 09/11] leds: backlight trigger: Move blank-state handling into helper Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 10/11] leds: backlight trigger: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-26 9:32 ` [PATCH v2 11/11] fbdev: Remove constants of unused events Thomas Zimmermann
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=202502272207.A1uo13Zf-lkp@intel.com \
--to=lkp@intel.com \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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