linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12304/12343] drivers/nvme/host/fc.c:1914: undefined reference to `blkcg_get_fc_appid'
Date: Tue, 17 May 2022 23:19:04 +0800	[thread overview]
Message-ID: <202205172344.3GFeaum1-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   47c1c54d1bcd0a69a56b49473bc20f17b70e5242
commit: d199ae4cc6d8886b7f1c8048d0150168660e7f9f [12304/12343] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
config: microblaze-randconfig-s031-20220516 (https://download.01.org/0day-ci/archive/20220517/202205172344.3GFeaum1-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d199ae4cc6d8886b7f1c8048d0150168660e7f9f
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout d199ae4cc6d8886b7f1c8048d0150168660e7f9f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=microblaze SHELL=/bin/bash

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

   microblaze-linux-ld: drivers/nvme/host/fc.o: in function `nvme_fc_io_getuuid':
>> drivers/nvme/host/fc.c:1914: undefined reference to `blkcg_get_fc_appid'


vim +1914 drivers/nvme/host/fc.c

19fce0470f0503 James Smart 2020-12-01  1901  
980a0e068d14ac Muneendra   2022-05-10  1902  /*
980a0e068d14ac Muneendra   2022-05-10  1903   * nvme_fc_io_getuuid - Routine called to get the appid field
980a0e068d14ac Muneendra   2022-05-10  1904   * associated with request by the lldd
980a0e068d14ac Muneendra   2022-05-10  1905   * @req:IO request from nvme fc to driver
980a0e068d14ac Muneendra   2022-05-10  1906   * Returns: UUID if there is an appid associated with VM or
980a0e068d14ac Muneendra   2022-05-10  1907   * NULL if the user/libvirt has not set the appid to VM
980a0e068d14ac Muneendra   2022-05-10  1908   */
980a0e068d14ac Muneendra   2022-05-10  1909  char *nvme_fc_io_getuuid(struct nvmefc_fcp_req *req)
980a0e068d14ac Muneendra   2022-05-10  1910  {
980a0e068d14ac Muneendra   2022-05-10  1911  	struct nvme_fc_fcp_op *op = fcp_req_to_fcp_op(req);
980a0e068d14ac Muneendra   2022-05-10  1912  	struct request *rq = op->rq;
980a0e068d14ac Muneendra   2022-05-10  1913  
980a0e068d14ac Muneendra   2022-05-10 @1914  	return rq->bio ? blkcg_get_fc_appid(rq->bio) : NULL;
980a0e068d14ac Muneendra   2022-05-10  1915  }
980a0e068d14ac Muneendra   2022-05-10  1916  EXPORT_SYMBOL_GPL(nvme_fc_io_getuuid);
980a0e068d14ac Muneendra   2022-05-10  1917  

:::::: The code at line 1914 was first introduced by commit
:::::: 980a0e068d14ac82c78beb93c97e8e9a630367a3 scsi: nvme-fc: Add new routine nvme_fc_io_getuuid()

:::::: TO: Muneendra <muneendra.kumar@broadcom.com>
:::::: CC: Martin K. Petersen <martin.petersen@oracle.com>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-05-17 15:19 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=202205172344.3GFeaum1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=martin.petersen@oracle.com \
    /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