public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [linux-chenxing:mstar_v5_14_rebase_i2_drm 156/349] drivers/dma/mstar/mstar-msc313-cmdq.c:142:6: warning: no previous prototype for 'msc313_cmdq_issue_pending'
Date: Mon, 19 Jul 2021 08:59:51 +0800	[thread overview]
Message-ID: <202107190848.djjUa0Se-lkp@intel.com> (raw)

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

tree:   git://github.com/linux-chenxing/linux.git mstar_v5_14_rebase_i2_drm
head:   93dfb2364436067bf34c6d4ddcd282496182cc0f
commit: 8104b59f2bd1ea881f923e9de519dfd639185995 [156/349] MSC313: CMDQ dma
config: s390-allyesconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 10.3.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/linux-chenxing/linux/commit/8104b59f2bd1ea881f923e9de519dfd639185995
        git remote add linux-chenxing git://github.com/linux-chenxing/linux.git
        git fetch --no-tags linux-chenxing mstar_v5_14_rebase_i2_drm
        git checkout 8104b59f2bd1ea881f923e9de519dfd639185995
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=s390 

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/dma/mstar/mstar-msc313-cmdq.c: In function 'msc313_cmdq_irq':
   drivers/dma/mstar/mstar-msc313-cmdq.c:132:22: warning: unused variable 'cmdq' [-Wunused-variable]
     132 |  struct msc313_cmdq *cmdq = data;
         |                      ^~~~
   drivers/dma/mstar/mstar-msc313-cmdq.c: At top level:
>> drivers/dma/mstar/mstar-msc313-cmdq.c:142:6: warning: no previous prototype for 'msc313_cmdq_issue_pending' [-Wmissing-prototypes]
     142 | void msc313_cmdq_issue_pending(struct dma_chan *chan){
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/dma/mstar/mstar-msc313-cmdq.c: In function 'msc313_tx_submit':
>> drivers/dma/mstar/mstar-msc313-cmdq.c:148:2: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
     148 |  struct msc313_cmdq_desc *desc = to_desc(tx);
         |  ^~~~~~


vim +/msc313_cmdq_issue_pending +142 drivers/dma/mstar/mstar-msc313-cmdq.c

   141	
 > 142	void msc313_cmdq_issue_pending(struct dma_chan *chan){
   143		printk("cmdq issue pending\n");
   144	}
   145	
   146	static dma_cookie_t msc313_tx_submit(struct dma_async_tx_descriptor *tx){
   147		struct msc313_cmdq_chan *chan = to_chan(tx->chan);
 > 148		struct msc313_cmdq_desc *desc = to_desc(tx);
   149		list_add_tail(&desc->queue_node, &chan->queue);
   150		return chan->cookie++;
   151	}
   152	

---
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: 67026 bytes --]

                 reply	other threads:[~2021-07-19  1:00 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=202107190848.djjUa0Se-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=daniel@0x0f.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