public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alan Tull <atull@opensource.altera.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Dinh Nguyen <dinh.nguyen@intel.com>
Subject: [dinguyen:socfpga-5.14_v1 10/121] drivers/fpga/fpga-mgr-debugfs.h:30:6: warning: no previous prototype for 'fpga_mgr_debugfs_add'
Date: Fri, 5 Nov 2021 20:12:19 +0800	[thread overview]
Message-ID: <202111052013.f79RPg38-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2497 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git socfpga-5.14_v1
head:   cc7ba8d9b34b85acfbeefb77fa57c116c733c2c4
commit: 0f594e3dee07f3a29f4f5f1ac7e71887cf2f0f57 [10/121] FogBugz #398879-2: fpga mgr debugfs
config: sparc-buildonly-randconfig-r002-20211105 (attached as .config)
compiler: sparc-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://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/commit/?id=0f594e3dee07f3a29f4f5f1ac7e71887cf2f0f57
        git remote add dinguyen https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
        git fetch --no-tags dinguyen socfpga-5.14_v1
        git checkout 0f594e3dee07f3a29f4f5f1ac7e71887cf2f0f57
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=sparc 

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 >>):

   In file included from drivers/fpga/fpga-mgr.c:20:
>> drivers/fpga/fpga-mgr-debugfs.h:30:6: warning: no previous prototype for 'fpga_mgr_debugfs_add' [-Wmissing-prototypes]
      30 | void fpga_mgr_debugfs_add(struct fpga_manager *mgr) {}
         |      ^~~~~~~~~~~~~~~~~~~~
>> drivers/fpga/fpga-mgr-debugfs.h:31:6: warning: no previous prototype for 'fpga_mgr_debugfs_remove' [-Wmissing-prototypes]
      31 | void fpga_mgr_debugfs_remove(struct fpga_manager *mgr) {}
         |      ^~~~~~~~~~~~~~~~~~~~~~~
>> drivers/fpga/fpga-mgr-debugfs.h:32:6: warning: no previous prototype for 'fpga_mgr_debugfs_init' [-Wmissing-prototypes]
      32 | void fpga_mgr_debugfs_init(void) {}
         |      ^~~~~~~~~~~~~~~~~~~~~
>> drivers/fpga/fpga-mgr-debugfs.h:33:6: warning: no previous prototype for 'fpga_mgr_debugfs_uninit' [-Wmissing-prototypes]
      33 | void fpga_mgr_debugfs_uninit(void) {}
         |      ^~~~~~~~~~~~~~~~~~~~~~~


vim +/fpga_mgr_debugfs_add +30 drivers/fpga/fpga-mgr-debugfs.h

    29	
  > 30	void fpga_mgr_debugfs_add(struct fpga_manager *mgr) {}
  > 31	void fpga_mgr_debugfs_remove(struct fpga_manager *mgr) {}
  > 32	void fpga_mgr_debugfs_init(void) {}
  > 33	void fpga_mgr_debugfs_uninit(void) {}
    34	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27654 bytes --]

                 reply	other threads:[~2021-11-05 12:12 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=202111052013.f79RPg38-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=atull@opensource.altera.com \
    --cc=dinh.nguyen@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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