From: kernel test robot <lkp@intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jani.nikula@intel.com
Subject: Re: [PATCH 2/4] drm/i915/display: add intel_display_snapshot abstraction
Date: Wed, 4 Sep 2024 20:23:03 +0800 [thread overview]
Message-ID: <202409042040.doh7ZTmu-lkp@intel.com> (raw)
In-Reply-To: <f2cc41111504e062c3ecb287daee6967078b73cc.1725372032.git.jani.nikula@intel.com>
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20240904]
[cannot apply to drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.11-rc6]
[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/Jani-Nikula/drm-i915-dump-display-parameters-captured-in-error-state-not-current/20240903-220614
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link: https://lore.kernel.org/r/f2cc41111504e062c3ecb287daee6967078b73cc.1725372032.git.jani.nikula%40intel.com
patch subject: [PATCH 2/4] drm/i915/display: add intel_display_snapshot abstraction
config: i386-buildonly-randconfig-003-20240904 (https://download.01.org/0day-ci/archive/20240904/202409042040.doh7ZTmu-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240904/202409042040.doh7ZTmu-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/202409042040.doh7ZTmu-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/devfreq/governor_performance.o
>> ERROR: modpost: "intel_overlay_snapshot_capture" [drivers/gpu/drm/i915/i915.ko] undefined!
>> ERROR: modpost: "intel_overlay_snapshot_print" [drivers/gpu/drm/i915/i915.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-04 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:02 [PATCH 0/4] drm/i915/display: add snapshot capture/print infra Jani Nikula
2024-09-03 14:02 ` [PATCH 1/4] drm/i915: dump display parameters captured in error state, not current Jani Nikula
2024-09-05 16:43 ` Rodrigo Vivi
2024-09-03 14:02 ` [PATCH 2/4] drm/i915/display: add intel_display_snapshot abstraction Jani Nikula
2024-09-04 12:23 ` kernel test robot [this message]
2024-09-04 13:04 ` kernel test robot
2024-09-04 14:19 ` [PATCH v2] " Jani Nikula
2024-09-05 16:55 ` Rodrigo Vivi
2024-09-03 14:02 ` [PATCH 3/4] drm/i915/display: move device info and params handling to snapshot Jani Nikula
2024-09-05 16:56 ` Rodrigo Vivi
2024-09-03 14:03 ` [PATCH 4/4] drm/i915/display: move dmc snapshotting to new display snapshot Jani Nikula
2024-09-05 16:59 ` Rodrigo Vivi
2024-09-03 18:28 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: add snapshot capture/print infra Patchwork
2024-09-03 18:28 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-03 18:36 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-04 15:35 ` ✓ Fi.CI.BAT: success for drm/i915/display: add snapshot capture/print infra (rev2) Patchwork
2024-09-04 17:28 ` ✓ Fi.CI.IGT: success for drm/i915/display: add snapshot capture/print infra Patchwork
2024-09-05 13:25 ` ✗ Fi.CI.IGT: failure for drm/i915/display: add snapshot capture/print infra (rev2) Patchwork
2024-09-05 17:01 ` [PATCH 0/4] drm/i915/display: add snapshot capture/print infra Rodrigo Vivi
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=202409042040.doh7ZTmu-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=llvm@lists.linux.dev \
--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