From: kernel test robot <lkp@intel.com>
To: Uma Shankar <uma.shankar@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ville.syrjala@linux.intel.com, harry.wentland@amd.com,
pekka.paalanen@haloniitty.fi, sebastian.wick@redhat.com,
jadahl@redhat.com, mwen@igalia.com, contact@emersion.fr,
naveen1.kumar@intel.com, dmitry.baryshkov@linaro.org
Subject: Re: [v3 01/23] drm: color pipeline base work
Date: Thu, 6 Mar 2025 04:55:06 +0800 [thread overview]
Message-ID: <202503060428.qINtTEJ1-lkp@intel.com> (raw)
In-Reply-To: <20250305132608.2379253-2-uma.shankar@intel.com>
Hi Uma,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20250305]
[also build test WARNING on v6.14-rc5]
[cannot apply to drm-exynos/exynos-drm-next linus/master v6.14-rc5 v6.14-rc4 v6.14-rc3]
[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/Uma-Shankar/drm-color-pipeline-base-work/20250306-011827
base: next-20250305
patch link: https://lore.kernel.org/r/20250305132608.2379253-2-uma.shankar%40intel.com
patch subject: [v3 01/23] drm: color pipeline base work
config: i386-buildonly-randconfig-003-20250306 (https://download.01.org/0day-ci/archive/20250306/202503060428.qINtTEJ1-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250306/202503060428.qINtTEJ1-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/202503060428.qINtTEJ1-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_colorop.c:30:
In file included from include/drm/drm_plane.h:33:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2306:
include/linux/vmstat.h:507:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
507 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> drivers/gpu/drm/drm_colorop.c:162:6: warning: no previous prototype for function 'drm_colorop_cleanup' [-Wmissing-prototypes]
162 | void drm_colorop_cleanup(struct drm_colorop *colorop)
| ^
drivers/gpu/drm/drm_colorop.c:162:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
162 | void drm_colorop_cleanup(struct drm_colorop *colorop)
| ^
| static
2 warnings generated.
vim +/drm_colorop_cleanup +162 drivers/gpu/drm/drm_colorop.c
156
157 /**
158 * drm_colorop_cleanup - Cleanup a drm_colorop object in color_pipeline
159 *
160 * @colorop: The drm_colorop object to be cleaned
161 */
> 162 void drm_colorop_cleanup(struct drm_colorop *colorop)
163 {
164 struct drm_device *dev = colorop->dev;
165 struct drm_mode_config *config = &dev->mode_config;
166
167 list_del(&colorop->head);
168 config->num_colorop--;
169
170 if (colorop->state && colorop->state->data) {
171 drm_property_blob_put(colorop->state->data);
172 colorop->state->data = NULL;
173 }
174
175 kfree(colorop->state);
176 kfree(colorop);
177 }
178
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-05 20:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:25 [v3 00/23] Plane Color Pipeline support for Intel platforms Uma Shankar
2025-03-05 13:25 ` [v3 01/23] drm: color pipeline base work Uma Shankar
2025-03-05 19:29 ` kernel test robot
2025-03-05 20:33 ` kernel test robot
2025-03-05 20:55 ` kernel test robot [this message]
2025-03-05 13:25 ` [v3 02/23] drm: Add support for 3x3 CTM Uma Shankar
2025-03-05 13:25 ` [v3 03/23] drm: Add Enhanced LUT precision structure Uma Shankar
2025-03-05 13:25 ` [v3 04/23] drm: Add Color lut range attributes Uma Shankar
2025-03-05 13:25 ` [v3 05/23] drm: Add Color ops capability property Uma Shankar
2025-03-05 13:25 ` [v3 06/23] drm: Add 1D LUT multi-segmented color op Uma Shankar
2025-03-05 13:25 ` [v3 07/23] drm: Define helper to initialize segmented 1D LUT Uma Shankar
2025-03-05 13:25 ` [v3 08/23] drm/i915: Add identifiers for intel color blocks Uma Shankar
2025-03-05 13:25 ` [v3 09/23] drm/i915: Add intel_color_op Uma Shankar
2025-03-05 13:25 ` [v3 10/23] drm/i915/color: Add helper to create intel colorop Uma Shankar
2025-03-05 13:25 ` [v3 11/23] drm/i915/color: Create a transfer function color pipeline Uma Shankar
2025-03-05 13:25 ` [v3 12/23] drm/i915/color: Add and attach COLORPIPELINE plane property Uma Shankar
2025-03-05 13:25 ` [v3 13/23] drm/i915/color: Add framework to set colorop Uma Shankar
2025-03-05 13:25 ` [v3 14/23] drm/i915/color: Add callbacks to set plane CTM Uma Shankar
2025-03-05 13:26 ` [v3 15/23] drm/i915/color: Add new color callbacks for Xelpd Uma Shankar
2025-03-05 13:26 ` [v3 16/23] drm/i915/color: Add plane CTM callback for D13 and beyond Uma Shankar
2025-03-05 13:26 ` [v3 17/23] drm/i915: Add register definitions for Plane Degamma Uma Shankar
2025-03-05 13:26 ` [v3 18/23] drm/i915/color: Add framework to program PRE/POST CSC LUT Uma Shankar
2025-03-05 13:26 ` [v3 19/23] drm/i915: Add register definitions for Plane Post CSC Uma Shankar
2025-03-05 13:26 ` [v3 20/23] drm/i915/color: Program Pre-CSC registers Uma Shankar
2025-03-05 13:26 ` [v3 21/23] drm/i915/xelpd: Program Plane Post CSC Registers Uma Shankar
2025-03-05 13:26 ` [v3 22/23] drm/i915/color: Enable Plane Color Pipelines Uma Shankar
2025-03-05 13:26 ` [v3 23/23] drm/doc/rfc: Add documentation for multi-segmented 1D LUT Uma Shankar
2025-03-10 12:16 ` ✗ CI.Patch_applied: failure for Plane Color Pipeline support for Intel platforms (rev2) 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=202503060428.qINtTEJ1-lkp@intel.com \
--to=lkp@intel.com \
--cc=contact@emersion.fr \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=mwen@igalia.com \
--cc=naveen1.kumar@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pekka.paalanen@haloniitty.fi \
--cc=sebastian.wick@redhat.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@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