Linux Media Controller development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Petko Manolov <petko.manolov@konsulko.com>, linux-media@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	sakari.ailus@iki.fi, devicetree@vger.kernel.org,
	Petko Manolov <petko.manolov@konsulko.com>
Subject: Re: [PATCH v5 1/2] media: ovm6211: Adds support for OVM6211
Date: Thu, 10 Mar 2022 20:19:50 +0800	[thread overview]
Message-ID: <202203102030.LBUi85M1-lkp@intel.com> (raw)
In-Reply-To: <20220309102215.891001-2-petko.manolov@konsulko.com>

Hi Petko,

I love your patch! Perhaps something to improve:

[auto build test WARNING on 2b891d3980f6c255459d0e1c29ce2152ec7cf678]

url:    https://github.com/0day-ci/linux/commits/Petko-Manolov/media-ovm6211-Adds-support-for-OVM6211/20220309-182333
base:   2b891d3980f6c255459d0e1c29ce2152ec7cf678
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20220310/202203102030.LBUi85M1-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 276ca87382b8f16a65bddac700202924228982f6)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/4894c38df725fcab9dc9ac03d8cffa97971279b7
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Petko-Manolov/media-ovm6211-Adds-support-for-OVM6211/20220309-182333
        git checkout 4894c38df725fcab9dc9ac03d8cffa97971279b7
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/media/i2c/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> drivers/media/i2c/ovm6211.c:993:35: warning: unused variable 'ovm6211_id' [-Wunused-const-variable]
   static const struct i2c_device_id ovm6211_id[] = {
                                     ^
   1 warning generated.


vim +/ovm6211_id +993 drivers/media/i2c/ovm6211.c

   992	
 > 993	static const struct i2c_device_id ovm6211_id[] = {
   994		{ "ovm6211", 0 },
   995		{},
   996	};
   997	MODULE_DEVICE_TABLE(i2c, ovm6211_id);
   998	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

  parent reply	other threads:[~2022-03-10 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 10:22 [PATCH v5 0/2] media: ovm6211: Adds support for OVM6211 Petko Manolov
2022-03-09 10:22 ` [PATCH v5 1/2] " Petko Manolov
2022-03-09 11:51   ` Kieran Bingham
2022-03-09 12:56     ` Dave Stevenson
2022-03-10 12:19   ` kernel test robot [this message]
2022-04-19  9:42   ` Sakari Ailus
2022-03-09 10:22 ` [PATCH v5 2/2] dt-bindings: media: add ovti,ovm6211 bindings Petko Manolov
2022-03-09 13:59   ` Rob Herring
2022-03-09 16:20     ` Petko Manolov

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=202203102030.LBUi85M1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-media@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=petko.manolov@konsulko.com \
    --cc=sakari.ailus@iki.fi \
    /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