public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: popcornmix <popcornmix@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [l1k:smsc95xx_5.17 279/887] drivers/char/broadcom/rpivid-mem.c:52: warning: expecting prototype for rpivid(). Prototype was for DRIVER_NAME() instead
Date: Fri, 8 Apr 2022 17:11:38 +0800	[thread overview]
Message-ID: <202204081732.FRe9Lg4m-lkp@intel.com> (raw)

Hi popcornmix,

First bad commit (maybe != root cause):

tree:   https://github.com/l1k/linux smsc95xx_5.17
head:   05d68ced287b30f62f18f95b5476135ef669804a
commit: 369c3a505f84640f4c10f4caf67c22bf5f9b1d56 [279/887] char: Add broadcom char drivers back to build files
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20220408/202204081732.FRe9Lg4m-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
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/l1k/linux/commit/369c3a505f84640f4c10f4caf67c22bf5f9b1d56
        git remote add l1k https://github.com/l1k/linux
        git fetch --no-tags l1k smsc95xx_5.17
        git checkout 369c3a505f84640f4c10f4caf67c22bf5f9b1d56
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/char/broadcom/ drivers/gpu/drm/panel/

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/char/broadcom/rpivid-mem.c:52: warning: expecting prototype for rpivid(). Prototype was for DRIVER_NAME() instead
--
>> drivers/char/broadcom/bcm2835-gpiomem.c:2: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * GPIO memory device driver


vim +52 drivers/char/broadcom/rpivid-mem.c

8900af03fcebd0 Jonathan Bell 2019-05-09  51  
8900af03fcebd0 Jonathan Bell 2019-05-09 @52  #define DRIVER_NAME "rpivid-mem"
8900af03fcebd0 Jonathan Bell 2019-05-09  53  #define DEVICE_MINOR 0
8900af03fcebd0 Jonathan Bell 2019-05-09  54  

:::::: The code at line 52 was first introduced by commit
:::::: 8900af03fcebd0065244b505c394ce12164624d8 drivers: char: add chardev for mmap'ing the RPiVid control registers

:::::: TO: Jonathan Bell <jonathan@raspberrypi.org>
:::::: CC: Dom Cobley <popcornmix@gmail.com>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-08  9:18 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=202204081732.FRe9Lg4m-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=popcornmix@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