linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [hch-block:bio-poll 14/17] block/blk-exec.c:74:3: error: implicit declaration of function 'blk_poll'; did you mean 'bio_poll'?
Date: Fri, 30 Jul 2021 07:33:16 +0800	[thread overview]
Message-ID: <202107300709.RSIv7z5o-lkp@intel.com> (raw)

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

tree:   git://git.infradead.org/users/hch/block.git bio-poll
head:   82f07d9a4840e6b32c16f09eb13cc9f35dfec012
commit: 1cddcba54f697e136d5ad883741910a47b0b5415 [14/17] block: switch polling to be bio based
config: i386-randconfig-m021-20210728 (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce (this is a W=1 build):
        git remote add hch-block git://git.infradead.org/users/hch/block.git
        git fetch --no-tags hch-block bio-poll
        git checkout 1cddcba54f697e136d5ad883741910a47b0b5415
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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

All errors (new ones prefixed by >>):

   block/blk-exec.c: In function 'blk_rq_poll_completion':
>> block/blk-exec.c:74:3: error: implicit declaration of function 'blk_poll'; did you mean 'bio_poll'? [-Werror=implicit-function-declaration]
      74 |   blk_poll(rq->q, request_to_qc_t(rq->mq_hctx, rq), 0);
         |   ^~~~~~~~
         |   bio_poll
>> block/blk-exec.c:74:19: error: implicit declaration of function 'request_to_qc_t' [-Werror=implicit-function-declaration]
      74 |   blk_poll(rq->q, request_to_qc_t(rq->mq_hctx, rq), 0);
         |                   ^~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +74 block/blk-exec.c

c01b5a814e7b28 Keith Busch       2021-06-10  70  
c01b5a814e7b28 Keith Busch       2021-06-10  71  static void blk_rq_poll_completion(struct request *rq, struct completion *wait)
c01b5a814e7b28 Keith Busch       2021-06-10  72  {
c01b5a814e7b28 Keith Busch       2021-06-10  73  	do {
eba98c64b9805b Christoph Hellwig 2021-07-28 @74  		blk_poll(rq->q, request_to_qc_t(rq->mq_hctx, rq), 0);
c01b5a814e7b28 Keith Busch       2021-06-10  75  		cond_resched();
c01b5a814e7b28 Keith Busch       2021-06-10  76  	} while (!completion_done(wait));
c01b5a814e7b28 Keith Busch       2021-06-10  77  }
c01b5a814e7b28 Keith Busch       2021-06-10  78  

:::::: The code at line 74 was first introduced by commit
:::::: eba98c64b9805b630e9d44d47082fa239a0c7cbe block: replace the spin argument to blk_iopoll with a flags argument

:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Christoph Hellwig <hch@lst.de>

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

                 reply	other threads:[~2021-07-29 23:33 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=202107300709.RSIv7z5o-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --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;
as well as URLs for NNTP newsgroup(s).