All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-misc:nvme-ioctl 15/15] drivers/nvme/host/core.c:1946:23: error: implicit declaration of function 'nvme_find_path'
Date: Wed, 19 May 2021 20:36:32 +0800	[thread overview]
Message-ID: <202105192018.7bCSFBHR-lkp@intel.com> (raw)

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

tree:   git://git.infradead.org/users/hch/misc.git nvme-ioctl
head:   35c6dd73314831078d08613ffface7a97333169c
commit: 35c6dd73314831078d08613ffface7a97333169c [15/15] nvme: remove nvme_{get,put}_ns_from_disk
config: x86_64-randconfig-a003-20210519 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8e93d10633d751a3e9169bf9fa68326925ffa097)
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
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        git remote add hch-misc git://git.infradead.org/users/hch/misc.git
        git fetch --no-tags hch-misc nvme-ioctl
        git checkout 35c6dd73314831078d08613ffface7a97333169c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

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

All error/warnings (new ones prefixed by >>):

>> drivers/nvme/host/core.c:1946:23: error: implicit declaration of function 'nvme_find_path' [-Werror,-Wimplicit-function-declaration]
           struct nvme_ns *ns = nvme_find_path(head);
                                ^
>> drivers/nvme/host/core.c:1946:18: warning: incompatible integer to pointer conversion initializing 'struct nvme_ns *' with an expression of type 'int' [-Wint-conversion]
           struct nvme_ns *ns = nvme_find_path(head);
                           ^    ~~~~~~~~~~~~~~~~~~~~
   1 warning and 1 error generated.


vim +/nvme_find_path +1946 drivers/nvme/host/core.c

  1940	
  1941	static int nvme_send_ns_head_pr_command(struct block_device *bdev,
  1942			struct nvme_command *c, u8 data[16])
  1943	{
  1944		struct nvme_ns_head *head = bdev->bd_disk->private_data;
  1945		int srcu_idx = srcu_read_lock(&head->srcu);
> 1946		struct nvme_ns *ns = nvme_find_path(head);
  1947		int ret = -EWOULDBLOCK;
  1948	
  1949		if (ns) {
  1950			c->common.nsid = cpu_to_le32(ns->head->ns_id);
  1951			ret = nvme_submit_sync_cmd(ns->queue, c, data, 16);
  1952		}
  1953		srcu_read_unlock(&head->srcu, srcu_idx);
  1954		return ret;
  1955	}
  1956		
  1957	static int nvme_send_ns_pr_command(struct nvme_ns *ns, struct nvme_command *c,
  1958			u8 data[16])
  1959	{
  1960		c->common.nsid = cpu_to_le32(ns->head->ns_id);
  1961		return nvme_submit_sync_cmd(ns->queue, c, data, 16);
  1962	}
  1963	

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

                 reply	other threads:[~2021-05-19 12:36 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=202105192018.7bCSFBHR-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.