linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>
Subject: [linux-next:master 6891/7876] drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c:1007:16: sparse: sparse: symbol 'mdp5_plane_formats' was not declared. Should it be static?
Date: Wed, 24 Apr 2024 15:09:51 +0800	[thread overview]
Message-ID: <202404241522.oFguK9g2-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   a59668a9397e7245b26e9be85d23f242ff757ae8
commit: 6d602db2dd1cc80dda7b19b5c67e960ee7eb6f81 [6891/7876] drm/msm: add arrays listing formats supported by MDP4/MDP5 hardware
config: arc-randconfig-r122-20240424 (https://download.01.org/0day-ci/archive/20240424/202404241522.oFguK9g2-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240424/202404241522.oFguK9g2-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/202404241522.oFguK9g2-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c:1007:16: sparse: sparse: symbol 'mdp5_plane_formats' was not declared. Should it be static?

vim +/mdp5_plane_formats +1007 drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c

  1006	
> 1007	const uint32_t mdp5_plane_formats[] = {
  1008		DRM_FORMAT_ARGB8888,
  1009		DRM_FORMAT_ABGR8888,
  1010		DRM_FORMAT_RGBA8888,
  1011		DRM_FORMAT_BGRA8888,
  1012		DRM_FORMAT_XRGB8888,
  1013		DRM_FORMAT_XBGR8888,
  1014		DRM_FORMAT_RGBX8888,
  1015		DRM_FORMAT_BGRX8888,
  1016		DRM_FORMAT_RGB888,
  1017		DRM_FORMAT_BGR888,
  1018		DRM_FORMAT_RGB565,
  1019		DRM_FORMAT_BGR565,
  1020	
  1021		DRM_FORMAT_NV12,
  1022		DRM_FORMAT_NV21,
  1023		DRM_FORMAT_NV16,
  1024		DRM_FORMAT_NV61,
  1025		DRM_FORMAT_VYUY,
  1026		DRM_FORMAT_UYVY,
  1027		DRM_FORMAT_YUYV,
  1028		DRM_FORMAT_YVYU,
  1029		DRM_FORMAT_YUV420,
  1030		DRM_FORMAT_YVU420,
  1031	};
  1032	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-04-24  7:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202404241522.oFguK9g2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quic_abhinavk@quicinc.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