From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-block:remove-blk_get_request 13/18] block/blk-mq.c:2464:14: warning: no previous prototype for function 'blk_mq_request_issue_directly'
Date: Fri, 22 Oct 2021 08:26:33 +0800 [thread overview]
Message-ID: <202110220804.tcJET0ED-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3029 bytes --]
tree: git://git.infradead.org/users/hch/block.git remove-blk_get_request
head: 466175155bbbc600d2493d2e69518cd0fe84bce0
commit: d6c17b39384f838a79faff786e94da3b693ed0dc [13/18] block: move request based cloning helpers to blk-mq.c
config: hexagon-randconfig-r045-20211021 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 3cea2505fd8d99a9ba0cb625aecfe28a47c4e3f8)
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
git remote add hch-block git://git.infradead.org/users/hch/block.git
git fetch --no-tags hch-block remove-blk_get_request
git checkout d6c17b39384f838a79faff786e94da3b693ed0dc
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=hexagon
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 >>):
>> block/blk-mq.c:2464:14: warning: no previous prototype for function 'blk_mq_request_issue_directly' [-Wmissing-prototypes]
blk_status_t blk_mq_request_issue_directly(struct request *rq, bool last)
^
block/blk-mq.c:2464:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
blk_status_t blk_mq_request_issue_directly(struct request *rq, bool last)
^
static
1 warning generated.
vim +/blk_mq_request_issue_directly +2464 block/blk-mq.c
0f95549c0ea1e8 Mike Snitzer 2018-01-17 2463
fd9c40f64c514b Bart Van Assche 2019-04-04 @2464 blk_status_t blk_mq_request_issue_directly(struct request *rq, bool last)
fd9c40f64c514b Bart Van Assche 2019-04-04 2465 {
fd9c40f64c514b Bart Van Assche 2019-04-04 2466 blk_status_t ret;
fd9c40f64c514b Bart Van Assche 2019-04-04 2467 int srcu_idx;
fd9c40f64c514b Bart Van Assche 2019-04-04 2468 struct blk_mq_hw_ctx *hctx = rq->mq_hctx;
fd9c40f64c514b Bart Van Assche 2019-04-04 2469
fd9c40f64c514b Bart Van Assche 2019-04-04 2470 hctx_lock(hctx, &srcu_idx);
3e08773c3841e9 Christoph Hellwig 2021-10-12 2471 ret = __blk_mq_try_issue_directly(hctx, rq, true, last);
fd9c40f64c514b Bart Van Assche 2019-04-04 2472 hctx_unlock(hctx, srcu_idx);
fd9c40f64c514b Bart Van Assche 2019-04-04 2473
7f556a44e61d0b Jianchao Wang 2018-12-14 2474 return ret;
07068d5b8ed8fa Jens Axboe 2014-05-22 2475 }
07068d5b8ed8fa Jens Axboe 2014-05-22 2476
:::::: The code at line 2464 was first introduced by commit
:::::: fd9c40f64c514bdc585a21e2e33fa5f83ca8811b block: Revert v5.0 blk_mq_request_issue_directly() changes
:::::: TO: Bart Van Assche <bvanassche@acm.org>
:::::: CC: Jens Axboe <axboe@kernel.dk>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28086 bytes --]
reply other threads:[~2021-10-22 0:26 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=202110220804.tcJET0ED-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.