public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 5/5] adds i2c/ explicitly to Makefile
Date: Tue, 7 Dec 2021 06:56:54 +0800	[thread overview]
Message-ID: <202112070634.8UMBEkLw-lkp@intel.com> (raw)
In-Reply-To: <20211203221247.46324-6-petko.manolov@konsulko.com>

Hi Petko,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on v5.16-rc3]
[also build test WARNING on next-20211206]
[cannot apply to media-tree/master]
[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]

url:    https://github.com/0day-ci/linux/commits/Petko-Manolov/omv6211-linux-kernel-driver/20211204-061436
base:    d58071a8a76d779eedab38033ae4c821c30295a5
config: arm64-randconfig-r032-20211204 (https://download.01.org/0day-ci/archive/20211207/202112070634.8UMBEkLw-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 5f1d1854eb1450d352663ee732235893c5782237)
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
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/e3654b0a5fdd1f9b3488b69bf8cc1a2613788f83
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Petko-Manolov/omv6211-linux-kernel-driver/20211204-061436
        git checkout e3654b0a5fdd1f9b3488b69bf8cc1a2613788f83
        # 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=arm64 SHELL=/bin/bash drivers/staging/

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/staging/media/i2c/ovm6211.c:652:5: warning: no previous prototype for function 'ovm6211_set_pix_clk' [-Wmissing-prototypes]
   u32 ovm6211_set_pix_clk(struct ovm6211_dev *sensor, const struct ovm6211_mode_info *nm)
       ^
   drivers/staging/media/i2c/ovm6211.c:652:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   u32 ovm6211_set_pix_clk(struct ovm6211_dev *sensor, const struct ovm6211_mode_info *nm)
   ^
   static 
   1 warning generated.


vim +/ovm6211_set_pix_clk +652 drivers/staging/media/i2c/ovm6211.c

a3407db075daa0 Petko Manolov 2021-12-04  651  
a3407db075daa0 Petko Manolov 2021-12-04 @652  u32 ovm6211_set_pix_clk(struct ovm6211_dev *sensor, const struct ovm6211_mode_info *nm)
a3407db075daa0 Petko Manolov 2021-12-04  653  {
a3407db075daa0 Petko Manolov 2021-12-04  654  	u32 s, fmt, fps, ret;
a3407db075daa0 Petko Manolov 2021-12-04  655  
a3407db075daa0 Petko Manolov 2021-12-04  656  	/* x * y * [1|2] * y8/y10 * fps */
a3407db075daa0 Petko Manolov 2021-12-04  657  	s = nm->width * nm->height;
a3407db075daa0 Petko Manolov 2021-12-04  658  	fmt = 1;
a3407db075daa0 Petko Manolov 2021-12-04  659  	fps = ovm6211_framerates[sensor->cur_fr_id];
a3407db075daa0 Petko Manolov 2021-12-04  660  	ret = s * fmt * fps * 2;
a3407db075daa0 Petko Manolov 2021-12-04  661  
a3407db075daa0 Petko Manolov 2021-12-04  662  	return ret;
a3407db075daa0 Petko Manolov 2021-12-04  663  }
a3407db075daa0 Petko Manolov 2021-12-04  664  

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

           reply	other threads:[~2021-12-06 22:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20211203221247.46324-6-petko.manolov@konsulko.com>]

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=202112070634.8UMBEkLw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=petko.manolov@konsulko.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