All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Thierry Reding <treding@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thierryreding:for-6.3/work 176/176] drivers/soc/tegra/dce.c:149:23: error: implicit declaration of function 'FIELD_PREP'
Date: Sat, 21 Jan 2023 16:49:46 +0800	[thread overview]
Message-ID: <202301211622.MvVmacsc-lkp@intel.com> (raw)

tree:   https://github.com/thierryreding/linux for-6.3/work
head:   d2f9c8570d9db78d8edc29d02721fa315b564b4f
commit: d2f9c8570d9db78d8edc29d02721fa315b564b4f [176/176] WIP
config: arm-defconfig (https://download.01.org/0day-ci/archive/20230121/202301211622.MvVmacsc-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.0
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/thierryreding/linux/commit/d2f9c8570d9db78d8edc29d02721fa315b564b4f
        git remote add thierryreding https://github.com/thierryreding/linux
        git fetch --no-tags thierryreding for-6.3/work
        git checkout d2f9c8570d9db78d8edc29d02721fa315b564b4f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/soc/

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

All errors (new ones prefixed by >>):

   drivers/soc/tegra/dce.c: In function 'tegra_dce_boot_get_version':
>> drivers/soc/tegra/dce.c:149:23: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
     149 |         u32 command = FIELD_PREP(DCE_BOOT_CMD_COMMAND, DCE_BOOT_CMD_VERSION);
         |                       ^~~~~~~~~~
   drivers/soc/tegra/dce.c: In function 'tegra_dce_irq_callback':
>> drivers/soc/tegra/dce.c:429:16: error: implicit declaration of function 'FIELD_GET'; did you mean 'FOLL_GET'? [-Werror=implicit-function-declaration]
     429 |         type = FIELD_GET(DCE_IRQ_STATUS_TYPE, value);
         |                ^~~~~~~~~
         |                FOLL_GET
   cc1: some warnings being treated as errors


vim +/FIELD_PREP +149 drivers/soc/tegra/dce.c

   146	
   147	static int tegra_dce_boot_get_version(struct tegra_dce *dce, u32 *version)
   148	{
 > 149		u32 command = FIELD_PREP(DCE_BOOT_CMD_COMMAND, DCE_BOOT_CMD_VERSION);
   150		void *msg = (void *)(unsigned long)command;
   151		unsigned long status;
   152		int err;
   153	
   154		err = mbox_send_message(dce->boot.channel, msg);
   155		if (err < 0)
   156			return err;
   157	
   158		status = wait_for_completion_timeout(&dce->irq.done, 1000);
   159		if (status == 0)
   160			return -ETIMEDOUT;
   161	
   162		if (dce->boot.status < 0)
   163			return dce->boot.status;
   164	
   165		*version = dce->boot.status;
   166	
   167		return 0;
   168	}
   169	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

                 reply	other threads:[~2023-01-21  8:50 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=202301211622.MvVmacsc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=treding@nvidia.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 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.