mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	ezequiel@vanguardiasur.com.ar, p.zabel@pengutronix.de,
	mchehab@kernel.org, nicolas.dufresne@collabora.com
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>
Subject: Re: [PATCH] media: verisilicon: Add reference buffers compression
Date: Thu, 16 May 2024 05:39:48 +0800	[thread overview]
Message-ID: <202405160544.3hBso24H-lkp@intel.com> (raw)
In-Reply-To: <20240514162054.294002-1-benjamin.gaignard@collabora.com>

Hi Benjamin,

kernel test robot noticed the following build warnings:

[auto build test WARNING on media-tree/master]
[also build test WARNING on pza/reset/next linuxtv-media-stage/master linus/master v6.9 next-20240515]
[cannot apply to pza/imx-drm/next]
[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/Benjamin-Gaignard/media-verisilicon-Add-reference-buffers-compression/20240515-002208
base:   git://linuxtv.org/media_tree.git master
patch link:    https://lore.kernel.org/r/20240514162054.294002-1-benjamin.gaignard%40collabora.com
patch subject: [PATCH] media: verisilicon: Add reference buffers compression
config: alpha-randconfig-r133-20240515 (https://download.01.org/0day-ci/archive/20240516/202405160544.3hBso24H-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240516/202405160544.3hBso24H-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/202405160544.3hBso24H-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/media/platform/verisilicon/hantro_hevc.c:28:6: sparse: sparse: symbol 'hevc_use_compression' was not declared. Should it be static?

vim +/hevc_use_compression +28 drivers/media/platform/verisilicon/hantro_hevc.c

    27	
  > 28	bool hevc_use_compression;
    29	module_param_named(hevc_use_compression, hevc_use_compression, bool, 0644);
    30	MODULE_PARM_DESC(hevc_use_compression,
    31			 "Use reference frame compression for HEVC");
    32	

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

      parent reply	other threads:[~2024-05-15 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 16:20 Benjamin Gaignard
2024-05-15 17:31 ` Nicolas Dufresne
2024-05-16  7:49   ` Benjamin Gaignard
2024-05-15 21:39 ` kernel test robot [this message]

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=202405160544.3hBso24H-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=p.zabel@pengutronix.de \
    /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

all inboxes | Powered by JetHome®