From: kernel test robot <lkp@intel.com>
To: Uma Shankar <uma.shankar@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, ville.syrjala@linux.intel.com,
pekka.paalanen@collabora.com, contact@emersion.fr,
harry.wentland@amd.com, mwen@igalia.com, jadahl@redhat.com,
sebastian.wick@redhat.com, shashank.sharma@amd.com,
agoins@nvidia.com, joshua@froggi.es, mdaenzer@redhat.com,
aleixpol@kde.org, xaver.hugl@gmail.com, victoria@system76.com,
daniel@ffwll.ch, quic_naseer@quicinc.com,
quic_cbraga@quicinc.com, quic_abhinavk@quicinc.com,
arthurgrillo@riseup.net, marcan@marcan.st, Liviu.Dudau@arm.com,
sashamcintosh@google.com, sean@poorly.run,
Uma Shankar <uma.shankar@intel.com>
Subject: Re: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
Date: Fri, 16 Feb 2024 20:07:46 +0800 [thread overview]
Message-ID: <202402161931.6Z8xdViq-lkp@intel.com> (raw)
In-Reply-To: <20240213064835.139464-2-uma.shankar@intel.com>
Hi Uma,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next next-20240216]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes linus/master v6.8-rc4]
[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/20240213-144544
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20240213064835.139464-2-uma.shankar%40intel.com
patch subject: [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work
config: x86_64-randconfig-121-20240214 (https://download.01.org/0day-ci/archive/20240216/202402161931.6Z8xdViq-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240216/202402161931.6Z8xdViq-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/202402161931.6Z8xdViq-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vkms/vkms_colorop.c:11:11: sparse: sparse: symbol 'vkms_initialize_tf_pipeline' was not declared. Should it be static?
--
drivers/gpu/drm/vkms/vkms_composer.c: note: in included file:
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:29:29: sparse: sparse: symbol 'test_linear_lut' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:87:32: sparse: sparse: symbol 'test_matrix_3x4_50_desat' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_tests.c:146:32: sparse: sparse: symbol 'test_matrix_3x4_bt709_enc' was not declared. Should it be static?
vim +/vkms_initialize_tf_pipeline +11 drivers/gpu/drm/vkms/vkms_colorop.c
10
> 11 const int vkms_initialize_tf_pipeline(struct drm_plane *plane, struct drm_prop_enum_list *list)
12 {
13
14 struct drm_colorop *op, *prev_op;
15 struct drm_device *dev = plane->dev;
16 int ret;
17
18 /* 1st op: 1d curve */
19 op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
20 if (!op) {
21 DRM_ERROR("KMS: Failed to allocate colorop\n");
22 return -ENOMEM;
23 }
24
25 ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_1D_CURVE);
26 if (ret)
27 return ret;
28
29 list->type = op->base.id;
30 list->name = kasprintf(GFP_KERNEL, "Color Pipeline %d", op->base.id);
31
32 prev_op = op;
33
34 /* 2nd op: 3x4 matrix */
35 op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
36 if (!op) {
37 DRM_ERROR("KMS: Failed to allocate colorop\n");
38 return -ENOMEM;
39 }
40
41 ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_CTM_3X4);
42 if (ret)
43 return ret;
44
45 drm_colorop_set_next_property(prev_op, op);
46
47 prev_op = op;
48
49 /* 3rd op: 3x4 matrix */
50 op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
51 if (!op) {
52 DRM_ERROR("KMS: Failed to allocate colorop\n");
53 return -ENOMEM;
54 }
55
56 ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_CTM_3X4);
57 if (ret)
58 return ret;
59
60 drm_colorop_set_next_property(prev_op, op);
61
62 prev_op = op;
63
64 /* 4th op: 1d curve */
65 op = kzalloc(sizeof(struct drm_colorop), GFP_KERNEL);
66 if (!op) {
67 DRM_ERROR("KMS: Failed to allocate colorop\n");
68 return -ENOMEM;
69 }
70
71 ret = drm_colorop_init(dev, op, plane, DRM_COLOROP_1D_CURVE);
72 if (ret)
73 return ret;
74
75 drm_colorop_set_next_property(prev_op, op);
76
77 return 0;
78 }
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-16 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240213064835.139464-2-uma.shankar@intel.com>
2024-02-13 21:15 ` [PATCH 01/28] [NOT FOR REVIEW] drm: color pipeline base work kernel test robot
2024-02-14 2:46 ` kernel test robot
2024-02-16 12:07 ` kernel test robot [this message]
2024-02-17 16:56 ` kernel test robot
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=202402161931.6Z8xdViq-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liviu.Dudau@arm.com \
--cc=agoins@nvidia.com \
--cc=aleixpol@kde.org \
--cc=arthurgrillo@riseup.net \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=joshua@froggi.es \
--cc=marcan@marcan.st \
--cc=mdaenzer@redhat.com \
--cc=mwen@igalia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pekka.paalanen@collabora.com \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_cbraga@quicinc.com \
--cc=quic_naseer@quicinc.com \
--cc=sashamcintosh@google.com \
--cc=sean@poorly.run \
--cc=sebastian.wick@redhat.com \
--cc=shashank.sharma@amd.com \
--cc=uma.shankar@intel.com \
--cc=victoria@system76.com \
--cc=ville.syrjala@linux.intel.com \
--cc=xaver.hugl@gmail.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;
as well as URLs for NNTP newsgroup(s).