public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: hch <hch@lst.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, 0day robot <lkp@intel.com>
Subject: drivers/nvme/host/core.c:3629:50: error: use of undeclared identifier 'ctrl'
Date: Wed, 16 Mar 2022 18:52:37 +0800	[thread overview]
Message-ID: <202203161805.I9aAHZ66-lkp@intel.com> (raw)

tree:   https://github.com/0day-ci/linux/commits/UPDATE-20220315-151414/Sungup-Moon/driver-nvme-host-Support-duplicated-nsid-for-the-private-ns/20220314-191232
head:   7101b34f72a97926495a7befec1c27c502c1f792
commit: 7101b34f72a97926495a7befec1c27c502c1f792 driver/nvme/host: Support duplicated nsid for the private ns
date:   28 hours ago
config: hexagon-randconfig-r045-20220313 (https://download.01.org/0day-ci/archive/20220316/202203161805.I9aAHZ66-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a6ec1e3d798f8eab43fb3a91028c6ab04e115fcb)
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/0day-ci/linux/commit/7101b34f72a97926495a7befec1c27c502c1f792
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review UPDATE-20220315-151414/Sungup-Moon/driver-nvme-host-Support-duplicated-nsid-for-the-private-ns/20220314-191232
        git checkout 7101b34f72a97926495a7befec1c27c502c1f792
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/nvme/host/

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

>> drivers/nvme/host/core.c:3629:50: error: use of undeclared identifier 'ctrl'
                   if (h->ns_id != nsid || !nvme_is_uniqueue_nsid(ctrl, head))
                                                                  ^
>> drivers/nvme/host/core.c:3629:56: error: use of undeclared identifier 'head'
                   if (h->ns_id != nsid || !nvme_is_uniqueue_nsid(ctrl, head))
                                                                        ^
   2 errors generated.


vim +/ctrl +3629 drivers/nvme/host/core.c

  3615	
  3616	static struct nvme_ns_head *nvme_find_ns_head(struct nvme_subsystem *subsys,
  3617			unsigned nsid)
  3618	{
  3619		struct nvme_ns_head *h;
  3620	
  3621		lockdep_assert_held(&subsys->lock);
  3622	
  3623		list_for_each_entry(h, &subsys->nsheads, entry) {
  3624			/*
  3625			 * Private namespaces can share NSIDs under some conditions.
  3626			 * In that case we can't use the same ns_head for namespaces
  3627			 * with the same NSID.
  3628			 */
> 3629			if (h->ns_id != nsid || !nvme_is_uniqueue_nsid(ctrl, head))
  3630				continue;
  3631			if (!list_empty(&h->list) && nvme_tryget_ns_head(h))
  3632				return h;
  3633		}
  3634	
  3635		return NULL;
  3636	}
  3637	

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

                 reply	other threads:[~2022-03-16 10:53 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=202203161805.I9aAHZ66-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    /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