public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, jacopo.mondi@ideasonboard.com,
	laurent.pinchart@ideasonboard.com, martin.hecht@avnet.eu,
	michael.roeder@avnet.eu, linuxfancy@googlegroups.com,
	"Tommaso Merciai" <tomm.merciai@gmail.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	linux-media@vger.kernel.org,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Marco Felsch" <m.felsch@pengutronix.de>,
	"Gerald Loacker" <gerald.loacker@wolfvision.net>,
	"Shawn Tu" <shawnx.tu@intel.com>,
	"Krzysztof Hałasa" <khalasa@piap.pl>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Mikhail Rudenko" <mike.rudenko@gmail.com>,
	"Nicholas Roth" <nicholas@rothemail.net>,
	"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] media: i2c: Add support for alvium camera
Date: Wed, 7 Jun 2023 07:12:58 +0800	[thread overview]
Message-ID: <202306070716.28K0H9Jd-lkp@intel.com> (raw)
In-Reply-To: <20230606155416.260941-4-tomm.merciai@gmail.com>

Hi Tommaso,

kernel test robot noticed the following build warnings:

[auto build test WARNING on media-tree/master]
[also build test WARNING on robh/for-next linus/master v6.4-rc5 next-20230606]
[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/Tommaso-Merciai/dt-bindings-vendor-prefixes-Add-prefix-alliedvision/20230606-235632
base:   git://linuxtv.org/media_tree.git master
patch link:    https://lore.kernel.org/r/20230606155416.260941-4-tomm.merciai%40gmail.com
patch subject: [PATCH v3 3/3] media: i2c: Add support for alvium camera
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20230607/202306070716.28K0H9Jd-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
        mkdir -p ~/bin
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git remote add media-tree git://linuxtv.org/media_tree.git
        git fetch media-tree master
        git checkout media-tree/master
        b4 shazam https://lore.kernel.org/r/20230606155416.260941-4-tomm.merciai@gmail.com
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=mips olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/media/i2c/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306070716.28K0H9Jd-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/media/i2c/alvium-csi2.c: In function 'alvium_set_ctrl_white_balance':
>> drivers/media/i2c/alvium-csi2.c:2205:21: warning: variable 'blue_min' set but not used [-Wunused-but-set-variable]
    2205 |                 u64 blue_min;
         |                     ^~~~~~~~
>> drivers/media/i2c/alvium-csi2.c:2204:21: warning: variable 'blue_max' set but not used [-Wunused-but-set-variable]
    2204 |                 u64 blue_max;
         |                     ^~~~~~~~
>> drivers/media/i2c/alvium-csi2.c:2203:21: warning: variable 'red_min' set but not used [-Wunused-but-set-variable]
    2203 |                 u64 red_min;
         |                     ^~~~~~~
>> drivers/media/i2c/alvium-csi2.c:2202:21: warning: variable 'red_max' set but not used [-Wunused-but-set-variable]
    2202 |                 u64 red_max;
         |                     ^~~~~~~
   drivers/media/i2c/alvium-csi2.c: In function 'alvium_set_frame_interval':
>> drivers/media/i2c/alvium-csi2.c:2574:29: warning: variable 'max_fr' set but not used [-Wunused-but-set-variable]
    2574 |         u64 req_fr, min_fr, max_fr;
         |                             ^~~~~~
>> drivers/media/i2c/alvium-csi2.c:2574:21: warning: variable 'min_fr' set but not used [-Wunused-but-set-variable]
    2574 |         u64 req_fr, min_fr, max_fr;
         |                     ^~~~~~
   drivers/media/i2c/alvium-csi2.c: In function 'alvium_subdev_init':
>> drivers/media/i2c/alvium-csi2.c:3172:27: warning: variable 'crop' set but not used [-Wunused-but-set-variable]
    3172 |         struct v4l2_rect *crop;
         |                           ^~~~
>> drivers/media/i2c/alvium-csi2.c:3171:36: warning: variable 'fmt' set but not used [-Wunused-but-set-variable]
    3171 |         struct v4l2_mbus_framefmt *fmt;
         |                                    ^~~


vim +/blue_min +2205 drivers/media/i2c/alvium-csi2.c

  2186	
  2187	static int alvium_set_ctrl_white_balance(struct alvium_dev *alvium,
  2188					    bool awb)
  2189	{
  2190		struct alvium_ctrls *ctrls = &alvium->ctrls;
  2191		int ret = 0;
  2192	
  2193		if (ctrls->auto_wb->is_new) {
  2194			ret = alvium_set_awb(alvium, awb);
  2195			if (ret)
  2196				return ret;
  2197		}
  2198	
  2199		if (!awb && ctrls->auto_wb->is_new) {
  2200			u64 red = (u64)ctrls->red_balance->val;
  2201			u64 blue = (u64)ctrls->blue_balance->val;
> 2202			u64 red_max;
> 2203			u64 red_min;
> 2204			u64 blue_max;
> 2205			u64 blue_min;
  2206	
  2207			ret = alvium_get_red_balance_ratio_params(alvium);
  2208			if (ret)
  2209				return ret;
  2210	
  2211			ret = alvium_get_blue_balance_ratio_params(alvium);
  2212			if (ret)
  2213				return ret;
  2214	
  2215			red_max = alvium->max_rbalance;
  2216			red_min = alvium->min_rbalance;
  2217			blue_max = alvium->max_bbalance;
  2218			blue_min = alvium->min_rbalance;
  2219	
  2220			ret = alvium_set_red_balance_ratio(alvium, red);
  2221			if (ret)
  2222				return ret;
  2223	
  2224			ret = alvium_set_blue_balance_ratio(alvium, blue);
  2225			if (ret)
  2226				return ret;
  2227		}
  2228	
  2229		return ret;
  2230	}
  2231	

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

      reply	other threads:[~2023-06-06 23:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:54 [PATCH v3 0/3] media: i2c: Add support for alvium camera Tommaso Merciai
2023-06-06 15:54 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add prefix alliedvision Tommaso Merciai
2023-06-06 16:29   ` Laurent Pinchart
2023-06-06 18:02     ` Conor Dooley
2023-06-07  6:55   ` Krzysztof Kozlowski
2023-06-06 15:54 ` [PATCH v3 2/3] media: dt-bindings: alvium: add document YAML binding Tommaso Merciai
2023-06-06 16:31   ` Rob Herring
2023-06-06 16:36   ` Laurent Pinchart
2023-06-06 18:07     ` Conor Dooley
2023-06-06 18:17       ` Laurent Pinchart
2023-06-06 18:23         ` Conor Dooley
2023-06-07  7:16           ` Tommaso Merciai
2023-06-07  7:14       ` Tommaso Merciai
2023-06-07  7:21         ` Laurent Pinchart
2023-06-07 11:27           ` Tommaso Merciai
2023-06-07  7:11     ` Tommaso Merciai
2023-06-06 15:54 ` [PATCH v3 3/3] media: i2c: Add support for alvium camera Tommaso Merciai
2023-06-06 23:12   ` 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=202306070716.28K0H9Jd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=broonie@kernel.org \
    --cc=gerald.loacker@wolfvision.net \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=khalasa@piap.pl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxfancy@googlegroups.com \
    --cc=m.felsch@pengutronix.de \
    --cc=martin.hecht@avnet.eu \
    --cc=mchehab@kernel.org \
    --cc=michael.roeder@avnet.eu \
    --cc=mike.rudenko@gmail.com \
    --cc=nicholas@rothemail.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnx.tu@intel.com \
    --cc=tomm.merciai@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