From: kernel test robot <lkp@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, Lucas De Marchi <lucas.demarchi@intel.com>,
kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH v2 5/7] drm/i915/dmc: abstract GPU error state dump
Date: Tue, 22 Mar 2022 10:58:05 +0800 [thread overview]
Message-ID: <202203221023.tCblMieg-lkp@intel.com> (raw)
In-Reply-To: <2600c34a1a295456ed87fa64953a4530b0c001d2.1647870374.git.jani.nikula@intel.com>
Hi Jani,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next v5.17 next-20220321]
[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/0day-ci/linux/commits/Jani-Nikula/drm-i915-dmc-cleanups/20220321-215213
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220322/202203221023.tCblMieg-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/1e23e4b2519941d741e3489536b37823cece69d8
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jani-Nikula/drm-i915-dmc-cleanups/20220321-215213
git checkout 1e23e4b2519941d741e3489536b37823cece69d8
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/display/intel_dmc.c: In function 'intel_dmc_print_error_state':
>> drivers/gpu/drm/i915/display/intel_dmc.c:822:2: error: implicit declaration of function 'i915_error_printf' [-Werror=implicit-function-declaration]
822 | i915_error_printf(m, "DMC loaded: %s\n",
| ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/i915_error_printf +822 drivers/gpu/drm/i915/display/intel_dmc.c
813
814 void intel_dmc_print_error_state(struct drm_i915_error_state_buf *m,
815 struct drm_i915_private *i915)
816 {
817 struct intel_dmc *dmc = &i915->dmc;
818
819 if (!HAS_DMC(i915))
820 return;
821
> 822 i915_error_printf(m, "DMC loaded: %s\n",
823 str_yes_no(intel_dmc_has_payload(i915)));
824 i915_error_printf(m, "DMC fw version: %d.%d\n",
825 DMC_VERSION_MAJOR(dmc->version),
826 DMC_VERSION_MINOR(dmc->version));
827 }
828
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-03-22 2:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:50 [Intel-gfx] [PATCH v2 0/7] drm/i915/dmc: cleanups Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 1/7] drm/i915/dmc: simplify intel_dmc_load_program() conditions Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 2/7] drm/i915/dmc: move assert_dmc_loaded() to intel_dmc.c Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 3/7] drm/i915/dmc: move dmc debugfs " Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 4/7] drm/i915/dmc: fix i915_reg_t usage Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 5/7] drm/i915/dmc: abstract GPU error state dump Jani Nikula
2022-03-21 19:40 ` kernel test robot
2022-03-22 2:58 ` kernel test robot [this message]
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 6/7] drm/i915/dmc: hide DMC version macros Jani Nikula
2022-03-21 13:50 ` [Intel-gfx] [PATCH v2 7/7] drm/i915/dmc: split out dmc registers to a separate file Jani Nikula
2022-03-21 20:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc: cleanups (rev2) Patchwork
2022-03-21 20:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-21 20:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-22 5:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=202203221023.tCblMieg-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=lucas.demarchi@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